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

No annotations and no behavioral content in the description. Nothing about whether this is a pure calculation, whether price/shares are currency or units, or what the output represents.

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?

It is short, but the concision is under-specification, not efficiency — 'Market Cap: Market Cap' repeats itself and communicates nothing.

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?

A finance calculation tool with two inputs and no output schema, no annotations, and a tautological description leaves the agent with no way to know what it computes or returns. Completely inadequate.

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 the parameters 'price' and 'shares' are already documented by the schema (albeit thinly). The description adds nothing — the baseline 3 applies when the schema carries the parameter documentation.

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 is 'Market Cap: Market Cap' — a tautology that restates the name without stating what the tool actually does (compute a valuation from price and shares?). It does not distinguish itself from financial siblings like x402-market-overview or x402-price-earnings in any meaningful way.

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?

No when-to-use guidance, no alternatives, no prerequisites. The agent has no signal for choosing this over the dozens of other finance tools in the sibling set.

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