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

Annotations already disclose readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by naming returned fields, noting totals and cross-company top recipients, and clarifying that results are facts rather than investment advice. It does not cover freshness or pagination, but the annotations and output schema carry much of that burden.

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 compact and front-loaded: the resource and returned fields come first, followed by filtering scope and a brief disclaimer. Every sentence carries useful information with no redundant filler.

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?

Given the rich annotations, 100% schema description coverage, and presence of an output schema, the description provides enough context for an agent to select and invoke the tool correctly. It states the domain, returned data, filtering options, and scope without needing to duplicate structured 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?

Schema description coverage is 100%, so all four parameters are already documented in the input schema. The description reinforces ticker and minimum-size filtering but does not add new semantics for days or limit beyond what the schema provides. Baseline 3 is appropriate when 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?

The description clearly identifies the resource as federal government contract awards to public companies and lists the returned fields (agency, amount obligated, purpose, dates, totals, top recipients). It is specific enough to distinguish from unrelated siblings such as list_congress_trades or list_corporate_lobbying, though it does not explicitly name a direct alternative.

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?

It gives filtering modes — 'By ticker or across the market, with a minimum size' — which implies how to use the tool. However, it does not explicitly state when to use this tool versus siblings or any exclusions, leaving usage guidance implicit rather than explicit.

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