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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds real value beyond that by disclosing the return format (markdown) and that the entire page is returned ('full ... page'), which hints at potentially large responses. It stops short of describing behavior on an invalid or stale path.

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?

One sentence, front-loaded with the verb and resource, then the required precursor and concrete examples. No filler, and every clause (format, full page, path provenance, examples) carries distinct information.

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?

With an output schema present and full parameter coverage, the description needn't explain return values; it still names the format. For a single-parameter read tool with rich annotations, the one gap is what happens when the path is invalid or no longer matches a page.

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 documents the single path parameter at 100% coverage, setting a baseline of 3. The description goes beyond that by supplying concrete path format examples ('twig/data', 'site-builder/overview'), which tell the agent what a well-formed value looks like rather than just repeating the field description.

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 (Fetch), a specific resource (a full Total CMS documentation page), an output format (markdown), and the exact input (its path). The phrase 'as returned by docs_search' implicitly separates it from docs_search and docs_lookup, so an agent can distinguish retrieval-by-path from searching without opening a schema.

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 parenthetical 'as returned by docs_search' gives clear ordering context (search first, then fetch by path), which is the key usage decision for this tool. It does not explicitly exclude alternatives such as docs_lookup or list_guides, and the many doc-adjacent siblings make that omission noticeable, but the primary workflow is unambiguous.

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