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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the data window starts October 2018 and results include aggregates plus named top winners, which matters because there is no output schema. It does not contradict 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 tightly written sentences with zero filler, front-loading what the tool returns before giving the use case. Nothing is wasted or buried.

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 correctly enumerates what comes back (awards, dollars, top companies, recent contracts) and the historical window. The only meaningful omission is the meaning and default of the 'recent' parameter, which an agent would have to infer from the schema's default of 15.

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 coverage is 67%: city and state are documented in the schema, while the 'recent' parameter has no description anywhere. The description reinforces the location scoping (city and state) but says nothing about the count/limit semantics of 'recent', so it neither fully compensates for the gap nor adds much beyond the schema text.

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 and resource (shows VA HVAC and plumbing contracts at one location) with a precise scope: aggregated awards/dollars since October 2018, top winning companies, and recent contracts. It is clearly distinguishable from company-oriented siblings like company_profile and lookup_contract, which slice the same data by vendor or individual contract rather than by facility.

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?

It offers a use case ('understand a facility before bidding') but gives no explicit when-not conditions or named alternatives among the siblings (e.g., when to use location_contracts vs. company_profile). Usage is implied rather than routed.

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