Get Bond Events

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

Annotations already declare it read-only, idempotent, and non-destructive. The description adds context on the specific event types included and highlights relevance for tracking dates, but does not detail output structure or pagination. No contradictions with annotations.

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 that front-load the key information: event types and primary use case. Every sentence is necessary and efficient.

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 all parameters documented and annotations providing safety profile, the description is sufficient for an agent to understand the tool's output (lifecycle events) and typical use. Minor gap: no explicit mention of response format (array of events) but name and context imply it.

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 parameters are already well-documented. The description does not add extra meaning beyond what the schema provides, which is a baseline acceptable level.

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 retrieves bond lifecycle events (coupons, calls/offers, maturity, conversion) and emphasizes tracking offer and repayment dates. Distinguishes from sibling tools like get_bond_coupons which likely returns only coupons.

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?

Indicates it is a key tool for tracking offer and repayment dates, implying when to use it, but does not provide explicit guidance on when not to use or compare to alternative tools for specific event types.

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