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

With no annotations, the description carries the full burden and does so well: it discloses that output is provider-generated with references 'when available', warns to verify claims, notes the guest trial has no identity, that guest execution_status is unavailable, and that requestKey does not alter the shared cache. These are non-obvious behavioral traits an agent needs.

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 purpose is front-loaded, but several trailing sentences are cryptic and under-explained ('Guest execution_status is unavailable.', 'Preserve arguments after uncertainty.'), which cost clarity without clearly earning their place in a short definition.

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 nested-argument tool with no output schema, the description covers return content (provider-generated explanation with references), security boundaries, caching semantics, and guest limitations. It is close to complete, missing only explicit sibling differentiation.

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 only 50% (only requestKey is documented in-schema), so the description compensates by specifying repoName format ('owner/repository') and clarifying requestKey's optionality and caching behavior. The 'question' parameter is left only to its name and maxLength, which is a minor gap.

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?

States a specific verb ('Ask a bounded question') and resource ('one public GitHub repository indexed by DeepWiki'), making the operation clear. It does not explicitly distinguish itself from the sibling free_deepwiki-public-structure tool, so an agent must infer the difference between asking a question versus retrieving structure.

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 the context (public repo, bounded question, guest trial) but never names alternatives or states when-not to use it versus free_deepwiki-public-structure or free_agenthub-free-guidance. The security constraint ('Never send private code or secrets') is helpful but is a restriction, not routing guidance.

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