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

The description goes far beyond the annotations by detailing 'DESTRUCTIVE. Splits and submits real exchange orders over time. Irreversible fills once slices execute. Not a simulation.' It also discloses auth requirements (X-Api-Key, linked exchange credentials), cost ($0.015 USDC per call), rate limit (10/min), and explicitly distinguishes billing from side effects. This is comprehensive behavioral disclosure.

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-sectioned and front-loaded, but it repeats the purpose twice (first sentence and the 'Purpose:' line). This redundancy adds bulk without new information. The remaining content is valuable, but the duplication prevents a higher score.

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 destructive execution tool with an output schema, the description covers all necessary context: auth, cost, rate limit, return values, safety guidelines, and human-confirmation requirements. It leaves no major gaps for an agent to safely invoke the 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?

Although schema coverage is 100%, the schema descriptions are generic ('Parameter `side` (string). Required.'). The tool description adds meaningful context by explaining the mechanism ('splits large orders into smaller randomized slices over configurable time windows'), implicitly clarifying total_size, slices, and duration_minutes. It also describes expected outputs (filled slices, average fill price, remaining quantity).

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's function: 'Time-Weighted Average Price execution engine — splits large orders into smaller randomized slices over configurable time windows to minimize market impact.' It uses a specific verb ('splits') and resource ('large orders'), and explicitly contrasts with simulation ('Not a simulation'), distinguishing it from sibling analysis/backtest tools.

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?

It provides explicit guidance: 'Prefer paper/simulation paths. For live money require explicit human confirmation (confirm_live / action=execute).' This tells the agent when to use the tool and when to exercise caution, though it does not name specific alternative tools. The context is clear enough for appropriate selection.

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