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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioral value beyond that: the shape of the returned payload and a hard citation policy ('Quote and cite only from what this returns'), which governs how the agent may use the output. The 20-id cap is repeated from schema rather than newly disclosed.

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 verb and resource, then a payload enumeration followed by two short operational sentences. The keyword list inside the parentheses is dense but every item maps to a real return field; nothing is padding.

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 carries the burden of describing return contents and does so concretely, plus the batch limit and the citation constraint. An agent has enough to call it correctly and to know how to use the results.

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% for the single 'ids' parameter, including minLength/maxLength/maxItems and an example. The description reinforces the id format with a second namespace ('case:...', 'claim-check:...') and the per-call limit, but adds no meaningful semantics beyond the schema, so baseline 3 applies.

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 and resource ('get the full records for ids') and enumerates exactly what comes back: figures, ratings, verdicts, caveats, primary sources, link, and related ids. It implies the discovery-vs-retrieval split from siblings ('ids from the menus and lists'), but never explicitly names find_company_cases or find_practices as the path that produces those ids.

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?

Usage is implied rather than stated: ids are described as coming 'from the menus and lists', which tells an agent this is a follow-up lookup after discovery. There is no explicit when-to-use/when-not, and no alternative is named, so the agent must infer that query-based siblings like find_company_cases are for discovery and this is for hydration.

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