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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say what liquidity measure is returned, whether a snapshot or time series, or any freshness/rate behavior, leaving the behavioral burden entirely on the annotations.

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 single sentence is front-loaded and wastes no words, but its brevity reflects under-specification rather than tight writing. It occupies minimal space without conveying anything actionable.

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?

An output schema exists, so return value structure need not be explained. However, for a single-market lookup with three mutually optional identifiers, the description should at minimum say what is retrieved and how to identify the market; neither is present.

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% and all three identifiers (id, slug, condition_id) are documented in the schema itself, so the baseline of 3 applies. The description adds no guidance on which of the three optional identifiers to prefer when supplying a single market reference.

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 'Polymarket market liquidity' merely expands the tool name into a noun phrase; it names no verb (fetch, compute, list) and does not say whether it returns a liquidity metric, an order-book snapshot, or a history. It also fails to distinguish the tool from the many sibling polymarket tools such as polymarket_market_detail or polymarket_token_orderbook.

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?

There is no statement of when to use this tool, no prerequisites, and no pointer to alternative siblings. An agent has no basis for choosing between this and polymarket_market_detail, polymarket_token_spread, or polymarket_clob_market.

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