usas_get_agency_awards_summary

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

Adds critical context beyond readOnlyHint/openWorldHint: explains scope spans all award types, not just contracts, and how data differs by agency type. No contradiction with 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?

Efficient, front-loaded with purpose, then scope, warnings, alternatives. Slightly long but all sentences earn their 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?

No output schema, but description lists key output fields (transaction_count, obligations, latest_action_date). Explains scope and limitations fully, making tool well-understood.

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 50% (only toptierCode has description). Description gives example value for toptierCode but does not explain fiscalYear format or range. Adequate but could be more detailed.

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?

Clearly states verb 'get summary' and resource 'awards' for a fiscal year, listing output fields. Distinguishes from sibling usas_spending_over_time for contracts-only.

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?

Explicitly tells when to use alternative (usas_spending_over_time for contracts-only) and warns about benefit-heavy agency interpretation. Also advises resolving toptierCode via usas_get_agency_profile.

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