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

No annotations are provided, so the description carries the burden. It discloses the cost ($0.05 per call), payment methods, and that it's educational data not financial advice. However, it doesn't describe response format, error behavior, or any rate limits. The payment mechanism is well explained, but other behavioral aspects are missing.

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 a single dense paragraph that front-loads the core purpose but then includes a long payment explanation. It's not overly long, but the payment details could be more concise. The structure is acceptable but could be improved with clearer separation of purpose and usage.

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?

Given the tool has one parameter and no output schema, the description covers the main purpose and payment, but lacks details on how to get condition_id, what the response looks like, and how this tool fits with siblings. For a paid API tool, more operational context would be helpful, but it's minimally adequate.

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%, and the description only mentions 'by condition_id' without explaining what a condition_id is or how to obtain it. The single parameter is required but its format, source, or examples are not provided. The description adds minimal value beyond the schema's field name.

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 aggregates wallet intelligence for one Polymarket market by condition_id, listing specific metrics (unique wallets, buy/sell volume split, new-wallet count, top-10 buyers). It distinguishes from siblings by specifying 'one market' and the condition_id parameter, though it doesn't explicitly name alternative tools for broader market views.

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 implies usage for a single market's stats but doesn't explicitly state when to use this vs. sibling tools like get_polymarket_market_landscape or get_polymarket_whales. It does provide payment instructions and mentions browsing all tools with get_catalog, which gives some context, but lacks clear when-to-use/when-not-to-use guidance.

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