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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. Beyond that the description adds only a source citation; it does not say whether the definitions are static reference data or live rollups, what scope they cover (banks vs. credit unions), or whether results change over time.

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 sentences, front-loaded with the subject and with no filler or repetition. It is efficiently written; the brevity is a virtue here rather than padding, though it leaves the definition thin overall.

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 and no parameters, the description is the only place an agent can learn what comes back, and it does not say. For a lookup tool surrounded by similar peer-related siblings, this leaves the agent unable to judge relevance without calling it.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond the schema. Baseline 4 applies for a no-arg tool whose schema is trivially complete.

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 a resource ('peer-group definitions and rollups') and attributes a source, so the general subject is clear. But it never states what the tool actually returns (a list of definitions? a mapping of institutions to peer groups? precomputed aggregates?) and gives no signal distinguishing it from siblings like peer_analysis, peer_comparison, or bank_peer_ranking.

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 when-to-use guidance at all — no indication of which questions this answers versus peer_analysis or peer_comparison, no prerequisites, and no exclusions. The 'Source: BankRegReports' note is provenance, not usage guidance.

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