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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: quarterly update cadence, the 0-100 score range, the 1-5 band scale, and an instruction to quote rank_in_history.reading beside the band label. It stops short of describing error/no-data behavior.

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?

Front-loaded with purpose and cadence, then a dense enumeration of returned fields. Given the absence of an output schema, the enumeration earns its length, though 'the methodology reading of the inputs' is vague enough to be dead weight as written.

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, the description carries the full burden of explaining returns, and it does so thoroughly: composite score, band and label, historical rank, methodology reading, and all five domains with member component percentiles. Combined with annotations covering the safety profile, an agent has what it needs to call and interpret this correctly.

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 the baseline is 4 and there is nothing to document. The description correctly implies a parameterless call and puts the detail into return-value semantics instead.

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 verb and resource: 'Fetch the latest quarterly reading of the American Distress Index (ADI) composite.' The resource is clearly distinct from the sibling indicator tools, though the description never names those siblings or distinguishes itself from get_indicator/get_county_scorecard explicitly.

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?

Usage is only implied: it is the tool for the ADI composite, and 'Updated quarterly' hints at refresh cadence. There is no explicit 'use this when / use get_indicator instead when' routing, and no guidance on what to do if a quarter hasn't been published.

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