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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real value beyond that: it says the response contains dates, source URL, missing evidence and a content hash, and it discloses the 160-character combined selection bound and the exclusion of inferred figures.

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?

Three tight sentences: purpose first, return/scope second, constraint last. The example slug earns its place, and nothing is redundant, though the 160-character bound sentence is somewhat dense.

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 rich annotations and an output schema present, the description needn't explain return values, and it supplies the selection constraint and scope exclusions an agent needs. What remains unstated is any guidance on picking this workflow over the many sibling financial_evidence_* tools.

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 0%, so the description must carry the param semantics, and it largely does: it explains that IDs are 'exact institution slugs', gives a concrete example ('au-sfb'), and states the 1-to-5 count bound. It does not restate the slug regex pattern, but the example conveys the expected format.

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 pairs a specific verb ('Review public disclosure coverage') with a precise resource ('institution monitoring record' for 'one to five exact institution slugs'). It explicitly scopes out inference of private balances, credit ratings and regulatory compliance, which separates it from analytics-flavored siblings, though it never names an alternative tool.

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 context is implied clearly: use this to check disclosure coverage for known institution slugs. The 'Does not infer...' sentence adds boundary guidance, but no sibling tool is named and there is no explicit when-to-use-this-vs-that routing statement.

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