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

Annotations already establish the safe-read profile (readOnly, idempotent, non-destructive). The description adds genuinely useful behavioral context beyond that: data is served 'from the existing cache' (implying possible staleness) and 'Reports pending data honestly' (implying some fields may be pending). These caveats are not in the structured fields.

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 short, front-loaded sentences with the resource named first. 'Reports pending data honestly' is slightly editorial and could be tightened, but there is no filler bloat.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, the description is thin for a tool with three fully undocumented parameters and no usage routing, leaving meaningful gaps.

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 0%, so the description carries the full burden of explaining limit, query, and offset. It mentions none of them, leaving all three parameters undocumented in both schema and prose, which is a real gap for a searchable/paginated endpoint.

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 ('Read') and names concrete resources ('AB5D institutional holdings and public credit lines'), plus scope ('from the existing cache'). It is clearer than a tautology, but it never distinguishes itself from related siblings such as get_donor_credits or search_public_collectors, and 'AB5D' is undefined jargon.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. Siblings like get_donor_credits and search_public_collectors overlap conceptually, yet the description offers nothing to route the agent between them.

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