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

With no annotations provided, the description carries the behavioral burden and does substantial work: it discloses the per-call price, x402/USDC payment flow, bearer/key/query auth fallback, limit cap, and educational purpose. It does not discuss response shape or rate limits, but the core operational behaviors are well covered.

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 more verbose than minimal, but the extra sentences about payment, auth, and catalog browsing are actionable for invocation. Core purpose and filters are front-loaded, and pricing appears first.

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 data retrieval tool with no output schema, the description explains return content, available filters, limits, pricing, and authentication well. It lacks explicit sibling differentiation but is otherwise complete enough for an agent to select and invoke it.

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?

The input schema has no parameter descriptions and 0% coverage, so the description fully compensates by enumerating the category filter values and documenting limit default/cap (100/2000). This gives both parameters meaningful semantics beyond their raw types.

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 identifies the tool as returning the full Polymarket market landscape with category-grouped odds, liquidity, volume, and direction, plus optional category and limit filters. It does not explicitly differentiate from sibling Polymarket tools like get_polymarket_market_stats, so it misses the top sibling-differentiation credit.

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 the use case: use this when you need a broad Polymarket landscape or a category-filtered subset. It does not state when to prefer this over sibling Polymarket intelligence tools or when not to use it.

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