fetch_doc

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

Annotations include readOnlyHint=true, already indicating a safe read operation. The description adds value by disclosing the output format (clean Markdown, ready for LLM consumption) and the URL domain constraint, which goes beyond the annotation.

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 description is three sentences, front-loaded with the primary action, and every sentence contributes essential information: what it does, what it returns, and usage guidance. No fluff.

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?

Given the tool's simple fetch operation, the presence of a full input schema (100% coverage), and an output schema, the description covers purpose, usage, and return format sufficiently. It also integrates with sibling search_docs, making it contextually 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 description coverage is 100%, so the baseline is 3. The description adds a specific behavioral constraint for the url parameter ('must start with https://docs.ansible.com/ or https://docs.redhat.com/') that is not fully explicit in the schema's short parameter description, adding meaningful guidance.

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 fetches a page from specific domains (docs.ansible.com or docs.redhat.com) and converts it to clean Markdown. It also differentiates from sibling search tools by emphasizing it fetches known URLs rather than searching.

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 explicitly says to 'Use search_docs to discover relevant page URLs, or pass a known URL directly', providing a clear alternative and usage context. It also imposes a URL prefix requirement, guiding when the tool is applicable.

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