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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the spread is not free money, each issuer carries its own credit/redemption/transfer restrictions, and the cheapest wrapper is often cheapest for a reason. This goes beyond the annotations and prevents a common misuse. It doesn't describe pagination or return format, but with no output schema and a simple limit param, that's a minor gap.

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 well-structured: a clear definition, a concrete example, an explicit exclusion, and a critical caveat. Every sentence earns its place. It's front-loaded with the core concept and ends with the most important usage warning. No fluff.

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?

For a read-only list tool with one optional param and no output schema, the description is nearly complete. It explains the concept, the scope, the limitation vs. underlying stock, and the risk of misinterpretation. The only missing piece is what the response looks like (e.g., list of wrappers with spread percentages), but the description's example gives a strong hint. Given the tool's simplicity, this is a high score.

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 0%, so the description must compensate. The description doesn't explicitly explain the 'limit' parameter, but the tool is a simple list with a single optional limit param, and the default is 40. The description's focus on the concept rather than the param is acceptable because the param is self-explanatory. However, it could have mentioned that limit controls the number of wrapper pairs returned. Given the low schema coverage, a 4 is fair.

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 and resource: it computes a cross-wrapper spread for tokenized equities, comparing every issuer that tokenizes the same real company. It clearly distinguishes itself from a comparison against the underlying stock, which is a different tool/feed. The concrete SpaceX example makes the purpose immediately graspable.

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 explicitly says when to use this tool: for cross-wrapper comparisons, and explicitly says when NOT to use it: not for comparing against the underlying stock, because that needs a licensed equity feed. It also warns against presenting the spread as arbitrage, which is a clear usage boundary. This is exemplary guidance.

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