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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data behavior are covered. The description adds useful context by identifying USAspending.gov as the source, but says nothing about pagination, rate limits, result volume, or what the returned awards contain — reasonable but not rich behavioral disclosure.

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?

A single front-loaded sentence with no filler; purpose and scope lead the sentence and the filter facets follow. Nothing in it is redundant.

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 8 optional parameters, full schema coverage, and no required inputs, the description is adequate for invocation, but with no output schema present it never characterizes the return payload (award records, fields, result caps), and it omits guidance on the all-optional-params default behavior. Adequate but with clear gaps.

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 description coverage is 100%, so every parameter is already documented with format hints (YYYY-MM-DD, 1-500, comma-separated state codes). The description merely restates the filter facets (keyword, NAICS, state, date, amount) and adds no syntax or default-behavior detail beyond the schema, so 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 ('Search'), a precise resource ('federal contract and grant awards'), and even names the data source ('official USAspending.gov API'). This is unmistakably distinct from the surrounding calc_* and permit/license siblings, so an agent can select it without opening the schema.

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 explicit when-to-use or when-not-to-use guidance, no mention of prerequisites, and no alternative tool named. The phrase 'by keyword, NAICS, state, date and amount' implies the filtering contexts but stops short of stating conditions for use, so it falls below the 'implied usage' bar.

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