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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the response format is Markdown, and a fragment identifier yields only one section rather than the whole document. It does not say what happens for an unknown id, which is the only notable gap.

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, front-loaded with what is returned, then the id forms, then the anchor modifier. No filler, and each sentence adds a distinct piece of callable 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 a single fully documented parameter, complete annotations and an output schema covering the return shape, the description supplies everything an agent needs: what it reads, what formats the id accepts, and how to narrow to a section.

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, but the description earns more by enumerating concrete accepted id shapes with examples ('work/sleep-anchor', '/about', a brentburgess.com URL, a brentburgess:// URI, 'consulting'). That is more actionable than the schema's abstract list of forms.

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 names a specific resource (post, case study, page, project) and states exactly what comes back: full Markdown text, or one section of it. It relates itself to siblings by noting the id comes from search or list_content, which helps the agent place it in the workflow, though it never states outright how it differs in purpose from search or list_content.

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?

Usage is implied rather than stated: the agent can infer this is the read step after search or list_content, and that '#anchor' retrieves a single section. There is no explicit when-to-use/when-not clause or named alternative for reading vs listing, so the agent must infer the routing.

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