get_docs_full

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

With no annotations, the description carries the behavioral burden and does disclose key expectations: returns a 'single consolidated file' and a 'large volume of text.' It warns the agent about the payload size. It doesn't detail return format or error behavior, but for a simple retrieval tool this is solid disclosure.

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?

Three sentences, each earning its place: the first defines what the tool does, the second states when to use it, and the third warns about output size and offers alternatives. Front-loaded and waste-free.

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 read-only retrieval tool with no output schema, the description covers the purpose, the usage scenario, the size caveat, and sibling alternatives. Nothing essential is missing for an agent to call it correctly.

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 100% of parameters with a clear description ('Name of the documentation set'), so the baseline is 3. The tool description does not add extra meaning to docName, but it doesn't need to since the schema already explains it.

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 opens with a specific verb and resource: 'Retrieves the complete documentation content in a single consolidated file.' It clearly distinguishes this tool from get_docs_page and search_docs by emphasizing the comprehensive, consolidated nature of the result.

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?

Explicitly says 'Use this when you need comprehensive knowledge or need to analyze the full documentation context' and then points to alternatives ('consider using get_docs_page or search_docs for targeted information'). This gives the agent a clear decision rule and names the alternatives.

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