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

No annotations exist, so the description carries the full burden. It discloses the data source, a lookback boundary (since 2010), the default filtering behavior, and the semantics of upcoming=true. It omits things like update frequency or pagination behavior, but the core behavioral traits are well covered.

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 sentences, both information-dense and front-loaded with the core purpose and source. Every clause earns its place, with no fluff or repetition.

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 a read-only retrieval tool with six optional parameters and no output schema, the description covers source, time range, default filter, upcoming behavior, and key returned fields. It does not explain how from/to interacts with upcoming or the default limit, but the schema handles parameter-level detail, making the description sufficiently complete.

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?

The schema covers 50% of parameters with descriptionsicki. The description adds meaning beyond the schema by explaining the default type (coupon auctions) and the behavior of upcoming=true, but it does not clarify limit, from/to interactions, or the 'all' enum value. It only partially compensates for the schema coverage gap.

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 states the resource (Treasury auction results and calendar from TreasuryDirect) and the specific data fields returned, making the tool's purpose unambiguous. It does not explicitly distinguish itself from sibling tools, so it falls short of a top score.

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 offers in-tool usage context by explaining the default coupon auction filter and the effect of upcoming=true, which helps an agent use the parameters. However, it never mentions when to choose this tool over alternatives like economic_calendar or policy_rates, leaving tool selection to inference.

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