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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds meaningful context on the return payload (health grade, star rating, Texas ratio, branch states, page link), which matters because there is no output schema. No authentication or error behavior for an invalid slug is mentioned.

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 dense sentences, zero filler, and the payload contents are front-loaded before the parameter instruction. Every clause earns its place.

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?

For a one-parameter read tool with no output schema, the description is nearly complete: it enumerates returned fields and explains where the slug comes from. Only edge behavior (invalid/unknown slug) is left unaddressed, a minor gap.

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% and the schema only declares `slug` as a bare string, so the description carries the load by explaining that the slug is the institution identifier obtained from search_institutions. That resolves the main ambiguity (format/provenance) an agent would hit.

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 resource (rates + health metrics for one bank or credit union) and enumerates exactly what it returns: deposit and loan rates, health letter grade, star rating, Texas ratio, branch states, and page link. The 'one bank or credit union' scoping clearly separates it from get_average_rates, get_best_rates, and search_institutions.

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?

The instruction 'Pass the slug from search_institutions' establishes the prerequisite lookup flow and points at the correct sibling for discovery. It does not explicitly state when to prefer this over, say, get_average_rates, but the single-institution scope implies that unambiguously.

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