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

With no annotations at all, the description carries the full burden, and it does disclose real behavior: a $0.01 USDC charge per call on Base is a paid-call/auth constraint an agent must know before invoking, and the slippage cap bounds the result. It still never states that the call is read-only and places no order, nor any rate or failure behavior.

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 densely packed sentence front-loads the core purpose, then lists outputs, pricing, and a disclaimer. No filler; the only slightly off-topic element is the 'Not advice' boilerplate.

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?

The enumeration of return values compensates for the absent output schema, and the cost line covers the missing annotations. But with no annotations, no output schema, and 0% parameter documentation, the undescribed token_id and the unstated read-only/no-order-placed nature leave the definition short of complete.

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 document both parameters and largely does not: 'shares' is clarified as a share count of one outcome, but token_id is never explained (identifier of which outcome, in what format). The agent is left to infer the key input from the phrase 'one outcome'.

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 uses a specific verb+resource ('Fill estimate for buying a number of shares of one outcome') and names the three quantities returned (VWAP, total cost, partial-fill status). It is clear on its own, but does not explicitly contrast itself with the sibling get_quote, which is the most likely point of confusion.

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?

'For buying' implicitly scopes the tool to buy-side, pre-trade estimation rather than selling or post-trade checks, and the slippage cap indicates it is a what-if calculation. However, no alternative is named and there is no explicit when-to-use/when-not statement relative to get_quote or get_status.

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