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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds the Markdown output shape and hints that non-exact slugs may resolve, but says nothing about failure behavior for a bad slug, caching, or whether results are stable.

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?

Front-loaded with the core action and format, then a single enumerated clause covering payload contents; every item earns its place because no output schema exists. The long run-on colon list would read better as bullets, keeping it just short of a 5.

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 no output schema, the description correctly compensates by enumerating what the agent receives, and it covers how to supply the single required parameter. Only the error/miss path for an invalid or guessed slug is unaddressed, which is a minor gap for a read-only 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 coverage is 100% and the schema already carries the example, so baseline is 3. The description goes further by explaining where the slug originates (search_fixes) and that guessed variants are accepted, which is actionable semantics not present in the schema.

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+resource ('Return one fix page') plus the return format (Markdown) and enumerates the page's actual sections. It is clearly distinguishable from siblings like get_post/get_tool, and it explicitly ties itself to search_fixes as the slug source.

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?

Gives clear context: get the slug from search_fixes, or pass a guessed variant. That tells the agent when to reach for this tool after searching. No explicit when-not or fallback guidance if the guessed slug misses, so it stops short of a 5.

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