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

No annotations are provided, so the description carries the full burden. It discloses that the operation is a list/filter action sourced from USAspending and identifies the filtering traits. However, it does not disclose pagination behavior, defaults for limit, data freshness, or whether authentication or specific prerequisites apply.

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?

One concise, front-loaded sentence states the core purpose, then lists the filter parameters. There is no filler or redundancy; every phrase earns its 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?

The definition is incomplete for an agent needing to invoke it correctly. There is no output schema, yet the description does not explain what the response contains. Parameter formats and defaults are unspecified, and there is no guidance on how this tool relates to sibling data sources. The sparse description leaves several operational 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 0%, so the description must compensate. It does add that agency, company_id, and limit are filters, but it does not define what agency refers to, what company_id represents, what values are accepted, or whether limit has a maximum/default. The parameter names alone carry most of the meaning.

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 states a specific action ('list'), a specific resource ('US federal contracts for drugs'), the product service code ('6505'), and the data source ('USAspending'). This clearly distinguishes it from sibling tools like list_drug_recalls and list_drug_shortages, which concern different datasets.

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 implies when to use the tool — when you need US federal drug contract data from USAspending — but it does not explicitly contrast it with alternatives or state when not to use it. Context from sibling names helps, but the description itself provides no explicit routing guidance.

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