godot_docs

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

Discloses version-matching and lists actions/params, but lacks details on error handling, response format (though output schema exists), and any potential side effects. No annotations provided, so description carries full burden.

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?

Single sentence plus concise listing. Every piece adds value, no redundancy. Front-loaded with key info.

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?

Covers core usage and parameters. Output schema exists but description doesn't reference it; slight improvement possible. For a tool with two actions and minimal schema, description is fairly 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?

Schema has generic 'action' and 'params' with no descriptions (0% coverage). Description compensates by defining allowed actions ('fetch', 'search') and expected parameters (class_name, method?, query). Adds significant meaning.

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?

Description clearly states the tool is for Godot official documentation, version-matched, with two specific actions (fetch and search). This distinguishes it from sibling tools like godot_node_read which read node properties.

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?

Implicitly, the tool is for documentation lookups, but no explicit guidance on when to use it vs alternatives. Sibling tools are diverse, but no other doc tool exists, so usage is straightforward.

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