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

The annotations already cover read-only and open-world behavior, lowering the bar. The description adds useful context beyond that: results are real-time and therefore volatile, scoped to active federal construction opportunities, and limited to opportunities tracked by RenovationRoute. This helps the agent set expectations about freshness and coverage.

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 tight sentences with no filler. The action and resource are front-loaded, and every clause adds either scope or output detail. It is appropriately sized for a zero-parameter stats tool.

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 parameters, no output schema, and annotations covering the safety profile, the description supplies the key decision facts: the universe covered (active federal construction opportunities tracked by RenovationRoute) and the three output categories. An agent can call the tool and know what to expect without needing exact field names or formatting details.

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 has zero parameters and an empty schema, so there is no parameter burden for the description to carry. The description instead tells the agent what the response will contain, which is the useful semantic information for this zero-input call.

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 ('Get a real-time snapshot of active federal construction opportunities') and then names the concrete outputs: total count, top states by volume, and contract value tier breakdown. This clearly distinguishes it from siblings like search_opportunities or get_opportunity, which imply list-level or record-level operations.

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 aggregate wording ('snapshot', 'total count', 'top states', 'breakdown') implies this is for high-level overviews rather than searching or retrieving specific records. However, it never explicitly names alternatives or states when not to use the tool, so the agent must infer the intended usage.

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