treasury-auction-calendar

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

Mentions 'Official government data, no API key' and lists output fields, but does not disclose data freshness, rate limits, or potential delays. With no annotations, more detail expected.

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 concise sentences covering purpose, filtering, and output. No wasted words.

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?

Fairly complete given 3 params and no output schema: describes data source, filter options, returned fields. Could add refresh frequency, but overall sufficient.

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 coverage is 100%, so baseline is 3. Description adds context (filtering by type and look-ahead) but adds little beyond schema descriptions.

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?

Clearly states it returns 'upcoming US Treasury auction schedule' and lists specific security types (Bills, Notes, Bonds, TIPS, FRNs). Distinct from sibling tools like 'treasury-yields' by being specific to auctions.

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?

Implies usage for getting auction schedules, but no explicit when-to-use or when-not-to-use guidance compared to alternatives. Lacks exclusionary context.

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