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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's 'List' verb is consistent with those. The description adds value beyond the annotations by disclosing that results are ranked by volume, limited to top states, and include a per-state count. No contradictions with the annotations.

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 tight sentences with zero filler. The primary verb, resource, and ranking behavior are front-loaded in the first sentence, and the second sentence adds the scope limitation that prevents misuse. 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 zero-parameter, read-only list tool with no output schema, the description covers everything needed to invoke it correctly: what is returned (states), how it is organized (ranked by volume), what the count is, and its top-N limitation. The tool is simple, and the description fully matches its complexity.

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 description is not obligated to explain argument semantics. The baseline for zero params is 4, and the description's mention of what each entry contains (state plus count) provides enough context to understand the result. No parameter documentation gap exists.

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 states a specific verb ('List'), a concrete resource ('US states with the most active federal construction opportunities on RenovationRoute'), and the output shape (ranked by volume, with count per state). The second sentence explicitly differentiates it from an exhaustive state list ('not an exhaustive list of all 50'), which distinguishes its scope from any sibling that might return full detail.

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 context is clear: this is the tool for a high-level, ranked state overview rather than per-opportunity detail. The 'not an exhaustive list of all 50' clause sets an explicit boundary on when it should not be used. However, it does not name sibling tools such as search_opportunities or get_stats or state conditions for preferring them, so it stops short of explicit alternative routing.

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