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

With no annotations provided, the description carries the full behavioral burden and does not meet it. It never states that this is a non-mutating read/compute operation, that an apiKey may be required for authenticated or metered access, or whether the optional paymentToken implies a paid/credit-consuming call — a material omission for a valuation API.

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?

A single dense sentence with no filler, front-loaded with the primary action and then the specific computed metrics. Every clause contributes information an agent can act on.

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 usefully enumerates the returned metrics, which is exactly what is needed to judge whether to call it. It falls short on behavioral context — authentication expectations, cost/credit implications of the optional paymentToken, and the asset_type enum's effect on results are all unaddressed for an 8-parameter tool.

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 88%, so the schema already documents cusip, apiKey, face_value, coupon_rate, market_price, paymentToken, and maturity_years with formats and defaults. The description adds no parameter-level detail beyond what the schema supplies, so the baseline of 3 applies. The only undocumented element is asset_type's enum semantics, which the description also does not address.

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 pairs a specific verb ('Calculates') with a specific resource (valuation metrics for CUSIPs) and enumerates the exact outputs produced: fair market value, YTM, modified duration, convexity, and jump-diffusion volatility intervals. An agent immediately knows this tool computes analytics rather than fetching a stored price. It is clearly distinct from the unrelated siblings (clearing fees, OFAC screening, key provisioning).

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 phrase 'secondary and distressed corporate debt CUSIPs' hints at the applicable instrument scope, but there is no explicit when-to-use guidance, no statement of prerequisites, and no reference to any alternative tool or method. The agent must infer usage context entirely.

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