SearchOpenCodeDocs

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses that the search returns 'contextual content with titles and direct links to the documentation pages,' which is a meaningful behavioral trait. It does not describe potential limitations like rate limits or result count, but for a simple search tool this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two well-structured sentences, front-loaded with the core action ('Search across the OpenCode knowledge base'), followed by usage context and return format. Every sentence earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter search tool with no output schema, the description is complete. It covers what the tool does, when to use it, and what it returns. Given the low complexity, the absence of additional constraints or result details is not a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter, which already includes guidance to 'Be specific for better results.' The description adds context about searching across the knowledge base but provides no additional syntax or format details, so it does not significantly enhance parameter semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it is a search tool across the OpenCode knowledge base, listing specific content types (configuration examples, CLI commands, guides) and return behavior (titles and direct links). This distinguishes it from sibling tools like GetOpenCodeDocPage or BrowseOpenCodeDocs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'Use this tool when you need to answer questions about OpenCode, find specific documentation, understand how features work, or locate implementation details.' This provides clear usage context. However, it does not mention when not to use it or explicitly compare it to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.