GetOpenCodeDocPage

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

With no annotations, the description carries the burden. It states the operation is a retrieval and returns 'full content', which is useful. However, it does not disclose error behavior, formatting, or any side effects; the read-only nature is implied but not explicitly stated.

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?

Two sentences: first states the function, second gives usage guidance. There is no redundancy or filler; every word earns its place.

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?

The description covers purpose, usage, and parameter context, which is adequate for a simple 1-parameter retrieval tool. It lacks explicit return-type details, but 'full content' implies the expected output. The absence of an output schema raises the bar slightly, but overall it is sufficiently complete.

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?

The schema covers the single 'path' parameter with examples, and the description also provides examples ('/docs/mcp-servers/', '/docs/agents/'). The description adds minimal beyond the schema, but it does reinforce the requirement of a known path.

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 the tool retrieves the full content of a specific OpenCode documentation page by path. The verb 'retrieve' and resource ('OpenCode documentation page') are specific, and the examples distinguish this from searching or browsing.

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?

It provides clear usage context: 'Use this when you need complete information from a known documentation page.' This implies alternatives (search/browse) for unknown pages, though it does not explicitly name them or state when not to use the tool.

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