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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that the returned content is exactly what the site renders (markdown format), and that listing returns all pages. This complements annotations with useful behavioral detail without contradiction.

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?

Two sentences, each conveying essential information without filler. The first sentence covers the two modes of operation; the second gives a concrete usage example. No wasted words.

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 listing/fetching tool with no output schema, the description fully covers behavior: listing returns all pages with metadata, fetching returns markdown, and a usage example. Sibling tools are unrelated, and context signals (one optional param) are well addressed.

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 100% with a clear description of the slug parameter. The description adds significant meaning by explaining that omitting slug lists all pages, while providing slug fetches that page. This conditional behavior is not captured in schema alone.

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 that without arguments the tool lists all documentation pages, and with a slug it fetches a single page. It names the specific resource (avizo.ro/docs) and actions (list, fetch), and the sibling tools are unrelated, so no confusion.

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 explains conditional usage: no argument for listing, slug argument for fetching. It provides examples of slugs like 'quickstart' and 'api-reference'. Though it doesn't mention when not to use, the conditional behavior is clear and sufficient for a documentation tool.

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