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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds valuable behavioral context by enumerating the exact metrics returned (daily changes, slopes, inversion flags, breakeven inflation, overnight rates from specific sources). It does not contradict annotations and adds content beyond them.

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 a single dense sentence that packs in all key elements without fluff. It front-loads the core resource ('US Treasury par and real (TIPS) yield curve') and then lists specifics. While efficient, the long comma-separated list could be slightly better structured, but it remains concise and information-dense.

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?

With no output schema, the description carries the full burden of explaining the tool's return. It lists all major components: par and real curves, daily changes, slopes, inversion flags, breakeven, and overnight rates from specific sources. It is fairly complete for a no-parameter tool, though it doesn't specify units, as-of timing, or how the data is organized—minor gaps given the tool's simplicity.

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 tool has zero parameters, and schema coverage is vacuously 100%. The description adds meaning by explaining what the tool returns, compensating for the lack of a formal output schema. It doesn't need to describe parameters since none exist.

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 verb ('get') and a precise resource ('US Treasury par and real (TIPS) yield curve') with detailed content (slopes, inversion flags, breakeven, overnight rates). It clearly distinguishes from siblings like get_treasury_auctions or get_market_summary by naming the exact dataset.

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 this is the tool for Treasury yield curve data but does not explicitly state when to use it versus alternatives (e.g., get_treasury_auctions for auctions, get_market_summary for a broader snapshot). No exclusions or alternative routing is provided, leaving selection to inference.

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