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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description's only extra content is a public-domain citation (17 U.S.C. § 105), which is nearly irrelevant to invocation; it says nothing about result volume, pagination, rate limits, fiscal-year coverage, or whether an empty recipient match returns nothing versus fuzzy matches.

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?

It is a single front-loaded sentence with no redundancy, so it is easy to scan. The statutory public-domain citation is arguably filler in a tool-selection context, keeping it just below top marks.

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?

There is no output schema, so the description bears full responsibility for telling the agent what comes back, and it does not: no indication of award fields (amount, agency, dates), result shape, or limits. For a data-query tool where return format drives downstream reasoning, this is a meaningful omission.

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 100% and the single 'recipient' parameter is documented with concrete examples (Palantir, SpaceX), so the schema carries the meaning. The description adds nothing about matching semantics (exact vs partial name, subsidiaries, spelling variants), which is the one piece of guidance the schema lacks. Baseline 3 applies.

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 gives a specific verb ('Query') and a specific resource ('USASpending.gov Federal Awards'), which is clearly distinct from every sibling (CFPB complaints, SEC EDGAR, deps.dev, etc.). The trailing phrase 'Contractor Intelligence' is vague marketing language that adds no verifiable scope, and it never says whether results are contracts, grants, or both.

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?

There is no when-to-use guidance, no stated prerequisites, and no mention of any alternative or companion tool for related lookups (e.g. corporate_kyb_and_risk_dossier, gleif_lei_kyb). The agent must infer from the name alone that this is the federal-award lookup tool.

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