investor_get_bond_calendar

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

With no annotations, the description must fully disclose behavior, but it only lists output types. It does not mention side effects, read-only nature, data freshness, error conditions, or any restrictions. The behavioral model is largely opaque.

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 very short, using a single sentence with bullet-like content. It is efficient and front-loaded, but lacks structure (e.g., separate usage notes). Still, it avoids unnecessary 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?

Given the lack of output schema and annotations, the description is incomplete. It does not clarify response format, pagination, date range behavior, or how account_ids affect results. Crucial context for a calendar tool is missing.

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 0% and the description does not explain the parameters horizon_days or account_ids. The tool's purpose implies a time horizon, but horizon_days is not linked to 'upcoming' events. No parameter meaning is conveyed.

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 tool provides a bond calendar with specific items: upcoming coupons, maturities, offers, maturity ladder, and 12m coupon income. It uniquely distinguishes the tool from siblings like investor_get_instrument or investor_get_portfolio.

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 no guidance on when to use this tool vs alternatives, nor does it provide context for prerequisites or exclusions. It only states what the tool does, not when it should be chosen.

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