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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, and openWorldHint false. The description adds valuable context beyond that by specifying the return format (full text Markdown), the inclusion of canonical URL and dates, and a citation instruction. It does not cover error behavior for invalid slugs, but the annotation bar is already met.

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?

The description is two tightly written sentences with the core action front-loaded. Every clause adds information: return format, scope, input source, accompanying metadata, and a usage instruction. No filler.

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 simple read-only retrieval tool with no output schema, the description is complete enough: it explains exactly what is returned, where the required slug comes from, and that the canonical URL should be cited. The annotations already cover safety traits, so no critical gaps remain.

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. The description adds meaning beyond the schema by specifying that the slug should come from list_guides, and the schema itself provides a realistic example and pattern. This provenance information is useful for correct invocation.

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 uses a specific verb ("Returns") and resource ("full text (Markdown) of one published CaseDaleel guide or composite case study"), and explicitly scopes retrieval "by slug from list_guides". It clearly distinguishes this full-content retrieval from sibling tools like list_guides and search_faq.

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 phrase "by slug from list_guides" gives clear context for when to call this tool: after obtaining a slug from list_guides. However, it does not explicitly state when not to use it or contrast it against search_faq or about_casedaleel, so it stops short of full when/when-not guidance.

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