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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds that the full article object is returned, but says nothing about behavior beyond the happy path — no auth requirements, rate limits, or what happens when a slug does not resolve.

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, front-loaded with the trigger condition, no filler. It is slightly redundant, since the first sentence already enumerates body, frontmatter, and checkpoints and the second repeats 'full article object including markdown content.'

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, a single fully documented required parameter, and annotations covering the read-only profile, the description is sufficient to select and call the tool. The only real gap is error behavior for a nonexistent slug, which is minor for a simple lookup.

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% and the single slug parameter is documented with concrete examples, so the schema does the heavy lifting. The description only restates 'by its slug' and adds no format, casing, or normalization details beyond that.

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 states a specific verb ('reading') and resource ('a specific technical article by its slug') plus the parts returned (Markdown body, frontmatter, checkpoints). It implicitly separates single-article retrieval from the plural listing sibling get_articles, but never names a sibling or explicitly contrasts behavior.

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?

'Use this tool when reading the complete ... body ... of a specific technical article by its slug' is an explicit trigger condition, so the agent knows the use case. There is no when-not guidance or named alternative (e.g., get_articles for listing), which keeps it below a 5.

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