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

With no annotations, the description carries the full burden. It usefully discloses the upstream source, the FY2008 coverage floor, and that rows are enriched with secCompany for listed recipients — a genuinely valuable behavioral detail. It says nothing about result caps (size max 100), pagination, rate limits, or whether filters combine with AND, which matters for an 11-param query tool.

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 tight sentences, front-loaded with the resource and source, with the enrichment note second. No filler or repetition of schema content.

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?

For an 11-parameter, zero-annotation, no-output-schema search tool, the description covers source and coverage but leaves defaults, filter-combination logic, and result-size behavior undocumented. Adequate but with clear gaps that an agent would have to resolve by trial.

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 the baseline is 3. The description adds no per-parameter meaning beyond noting the award-type categories, which the schema already enumerates; the schema does the heavy lifting.

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?

States the resource (federal awards), the source (USAspending.gov), the temporal scope (since FY2008), and the covered award types (contracts, IDVs, grants, loans). It does not explicitly differentiate itself from close siblings such as company_federal_awards or federal_award, though the secCompany note hints at its filtering/enrichment angle.

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 description gives no when-to-use or when-not-to-use guidance and names no alternatives among the many federal-award siblings (company_federal_awards, federal_award, federal_recipient, federal_recipients). An agent must infer from the schema alone that this is a general keyword/filter search.

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