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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds context beyond the annotations by specifying the document is 'public' and 'full,' which suggests no authentication and the complete scope of the return. This is useful behavioral information not present in the annotations.

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 first sentence is direct and front-loaded with the essential action. The second sentence about compatibility with ChatGPT deep research and company knowledge is somewhat vague and arguably does not earn its place, preventing a perfect score, but the overall length is appropriately short.

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 simple tool with one parameter, strong annotations, and no output schema, the description adequately communicates that the return is a full public discovery document. It lacks details about structure or error handling, but given the complexity, 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 input schema provides 100% coverage for the single 'id' parameter, clearly describing it as a 'Search result ID returned by the search tool.' The description adds no additional parameter semantics beyond restating that the fetch is 'by ID,' so the baseline score of 3 is appropriate.

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 precisely states 'Fetch the full public discovery document for a search result by ID,' using a specific verb and resource that clearly distinguishes it from sibling tools like search and get_project_summary. The annotation title reinforces this purpose.

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 implies a clear usage pattern: after obtaining a search result ID from the search tool, use fetch to retrieve the full document. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to know when to invoke this tool.

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