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

Annotations already declare this a read-only, idempotent, closed-world operation, so the safety profile is covered. The description contributes the returned data surface (history plus analytics plus outstanding amounts), but says nothing about result size, pagination, partial-data behavior, or what happens when a CUSIP is unknown. The heavy-volume warning lives in the schema, not here.

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 dense, front-loaded sentence opening with the verb and resource, then the payload, then the constraint. It is long but each clause maps to a distinct piece of information; minor compression would be possible but nothing is wasted.

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 burden of telling the agent what comes back, and it does so across all the major return categories. Missing pieces are minor for a read-only lookup: no mention of error behavior for invalid CUSIPs or result volume, though the latter is covered in the parameter schema.

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 three parameters are already documented, including the summarize/history tradeoff and the outstanding_on date semantics. The description's CUSIP-versus-description sentence adds a modest amount of meaning by clarifying what the required parameter accepts, but nothing beyond the schema baseline.

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?

Names a specific verb and resource ("Look up one Treasury security by CUSIP") and enumerates the returned content: terms, price history, duration/convexity/DV01/key-rate durations, TIPS and floater analytics, amount outstanding. It does not, however, distinguish itself from the adjacent list_treasury_securities or price_treasury_security tools, so an agent must still infer why this one rather than those.

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 closing sentence gives a real usage constraint — supply a CUSIP, not a descriptive phrase like "the current 10-year" — which steers the agent away from a natural but unsupported query form. Beyond that, there is no explicit when-to-use guidance and no named alternative for the overlapping list/price siblings.

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