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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the shape of the payload, including qualitative fields (evidence label, caveats) that signal data reliability, but says nothing about missing-slug behavior or whether entries can be absent.

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?

One compact clause with the key framing ('Full entry by slug') front-loaded, followed by a field list — no filler. The fragmentary grammar is terse but not ambiguous in this context.

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 present, the description usefully enumerates the returned fields, which is the main thing an agent needs to know. For a one-parameter read tool with clear annotations, nothing essential is missing beyond error behavior for unknown slugs.

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 single slug parameter is fully documented with an example, so the baseline is 3. The description contributes no additional semantics about slug format or normalization beyond what the schema already states.

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 'Full entry by slug' plus the enumerated fields (summary, outcome, metrics, evidence label, caveats, source links) makes it clear this retrieves a single full record rather than a list, which implicitly distinguishes it from the sibling search_use_cases. It stops short of an explicit verb like 'retrieve', relying on the title for that framing.

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?

No direct statement of when to choose this over search_use_cases; the workflow is only implied via the schema note that the slug comes from search_use_cases. An agent can infer the search-then-fetch pattern, but the description itself offers no explicit trigger condition or exclusion.

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