opencode-tool-compliance

OpenCode plugin tools require a standardized definition pattern with execute functions, context contracts, Zod schema validation for arguments, and TUI-safe logging to ensure consistency and safe operation across custom tool implementations.

The best way to validate arguments in OpenCode tool development is using Zod schema templates, which enforce robust argument validation and ensure tool definitions meet standardized compliance and safety requirements.

Yes, OpenCode plugin tools use Zod schemas to define argument validation and establish a consistent tool context contract, ensuring execute functions receive properly structured and validated inputs during execution.

OpenCode plugin tools need TUI-safe logging guidelines to prevent terminal interface corruption during execution, ensuring error handling and operational logs display correctly without disrupting the interactive environment.

OpenCode tool compliance applies to both new plugin development and refactoring existing custom tools, auditing definitions, contexts, and logging to enforce standardized structure, robust error handling, and safe operation across implementations.

Limitations involve adhering strictly to prescribed tool definition patterns and execute function structures, as custom implementations deviating from Zod schema templates and context contracts may not pass compliance audits.