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

Annotations already declare readOnlyHint=true, so the description is not required to repeat that. It adds useful context such as daily updates and the data source, but it does not disclose the conditional behavior around the optional 'days' parameter (Gold tier requirement) or describe the return format in detail. 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 two sentences and front-loaded with the core return value, followed by usage guidance. It is dense but not bloated; every clause carries information. A slight deduction for the long parenthetical and the list of fields making it a bit heavier than necessary.

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 no output schema, the description compensates by listing the return components (severity_index, severity_trend, complaint_count, servicer_breakdown, methodology_version) and the score range. It also gives context on historical data depth and update frequency. It is complete enough for an agent to invoke the tool and interpret the result, though field semantics are not explained.

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 description covers 100% of the single parameter ('days'), including its purpose and the Gold tier caveat, so the baseline is 3. The tool description itself does not add any extra semantics about parameters, merely implying history via 'history to 2012' and 'daily'.

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 returns a 0-100 complaint-velocity score with a specific methodology (NLP-severity-weighted daily complaint flow from CFPB) and enumerates the output fields. This specific verb+resource+scope makes its purpose unambiguous and distinguishes it from generic data tools.

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 provides explicit call scenarios ('when the user asks about servicer quality, borrower distress, or delinquency early warning') and lists application areas like credit-risk and SLABS decisions. However, it does not mention when not to use it or name alternative tools, so it falls short of a 5.

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