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

Annotations already declare read-only, non-destructive, idempotent and closed-world behavior, so the safety profile is covered. The description adds domain context that the payload reports stale/missing evidence and census counts rather than assessments. It does not explain freshness thresholds, what 'stale' means, or the shape of the counts.

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 clauses, front-loaded with the covered entity types and the data categories. No filler. The sentence-fragment style is terse but readable; slightly more structure would help.

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 must carry the burden of explaining return values. Naming 'coverage, stale/missing evidence and co-op census counts' gives a rough sense of the payload, but the units, grain and freshness semantics are left unspecified for a coverage-reporting tool.

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 50%: as_of is documented in the schema, while sector has an enum but no description. The description partially compensates by naming the Bank/SFB/UCB domain that maps to the sector enum values, but it says nothing about how as_of affects coverage or what the 'all' sector value returns.

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 names the resource precisely: evidence coverage counts for banks, small finance banks and urban co-operative banks, including stale/missing evidence and co-op census figures. The explicit 'Not a rating' distinguishes it from rating-oriented siblings such as bank_asset_quality_review and bank_npa_reconciliation. It lacks a clear verb ('reports'/'returns'), which keeps it from a 5.

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?

It says what the tool is and that it is 'Not a rating', which gives one negative cue, but never states when to call it versus alternatives like evidence_india, institution_research_coverage or institution_evidence_monitor. No prerequisites, no exclusions beyond the rating remark.

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