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

The annotations already indicate this is a safe, read-only, idempotent operation. The description adds useful behavioral context: it computes CRE relative to capital, flags concentration risks, and returns structured JSON, while noting it's based on public financial data. This goes beyond annotations but doesn't cover edge-case behaviors.

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 well-structured and concise: a clear opening sentence, a bulleted output list, and a brief note. Each section adds information without redundancy, making it easy for an agent to parse.

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?

Given the analytical complexity and multiple outputs, the description provides a good high-level overview of what is computed and returned. Since an output schema exists, it doesn't need to detail every field, but it does list the main output categories and the regulatory basis, which is sufficient for an agent to decide when to use 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?

Schema description coverage is 100%, so the schema already documents both parameters (cert and repdte) with exactly the needed syntax and defaults. The description adds no additional parameter-specific semantics, so a baseline score of 3 is appropriate.

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 states the tool analyzes loan portfolio composition and credit concentration risk for FDIC-insured institutions, with specifics like CRE concentration per 2006 interagency guidance. This distinguishes it from sibling analytical tools like funding profile or securities portfolio, which focus on other aspects.

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 implies usage through its focus on loan portfolio concentration, but does not explicitly state when to use it over alternatives or any exclusions. It provides context about the regulatory basis and data source, but lacks explicit 'when/when-not' guidance.

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