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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing that this is a safe read operation. The description adds context about the significance of CRA ratings (e.g., a 'Needs to Improve' rating can delay mergers), but it does not disclose other behavioral traits such as return format, pagination, or rate limits. This is adequate but not rich.

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?

The description is structured well, starting with usage guidance, then explaining the rating scale, a consequence, an example, and the source. All sentences contribute value, though the example sentence is slightly long and could be tightened. Overall, it is appropriately sized for the tool.

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 simple read-only tool with one parameter and no output schema, the description covers the use case, the meaning of the data, and gives an example of what results look like. The only notable gap is that it does not explicitly describe the return structure (e.g., rating, exam date, institution name), but the example implies it sufficiently for a low-complexity 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?

The schema has one parameter, institution_name, with no description (0% coverage). The description compensates partially by giving an example value ('Heartland Community Bank') and implying that the input is a bank name. However, it does not explicitly specify the expected format, such as full legal name vs. commonly used name, or whether an FDIC certificate number is acceptable.

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 clearly indicates the tool provides CRA ratings for banks, listing the rating categories and mentioning the FFIEC CRA Ratings Database as the source. It also gives a concrete example. However, it never explicitly states the action (e.g., 'retrieves' or 'returns'), relying on the tool name and context to convey the purpose.

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 description explicitly opens with 'Use when evaluating a bank's Community Reinvestment Act track record' and lists specific scenarios (merger application, charter acquisition, etc.). It does not mention alternatives or when not to use it, but the domain-specific use cases are clear and differentiate it from sibling tools.

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