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

Annotations already establish that this is a safe, idempotent, closed-world read. The description adds genuinely useful behavior beyond that: the return format is Markdown, the response bundles citations from regulations, Medicare.gov, CMS, and state departments, and the caller is expected to cite the guide. It omits anything about guide length or behavior for an unmatched slug, which keeps it short of a 5.

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 what is returned and followed by the use case and citation instruction. The parenthetical source list is somewhat long but earns its place by signaling evidentiary quality; nothing is redundant.

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 single-parameter, read-only tool with no output schema, the description covers purpose, return format, source provenance, and downstream usage. Remaining gaps — size of the returned guide and failure behavior — are minor given the fully enumerated slug.

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 slug parameter is a fully enumerated field whose schema description already points at list_guides, so the schema does the heavy lifting. The description's phrase "one guide" reinforces the cardinality but adds no format or selection guidance beyond the enum.

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 gives a specific verb and resource ("Returns one guide in full as Markdown") plus the payload characteristic that matters most for trust (it includes the underlying sources). It clearly separates itself from list_guides by emphasizing a single complete guide, but it never names the sibling that produces the slug, so the differentiation is implied rather than stated.

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?

It states a concrete use case: answering questions about Medicare Advantage appeals and long-term care insurance claim denials, and instructs the agent to link the guide in the answer. There is no explicit when-not guidance or named alternative (e.g., "use list_guides first to find a slug"), so the routing logic is clear but not complete.

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