list_markets

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It mentions that only active markets are listed and that sorting is by volume or liquidity, but it does not disclose pagination behavior, default limit handling, authentication needs, rate limits, or the read-only nature of the operation. Significant behavioral context is 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, efficient sentence with no wasted words. The verb and resource are front-loaded, and it conveys the core information compactly, though at the cost of missing important details.

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 details are covered. The description is minimally adequate for a simple list operation, but it leaves gaps around usage context, parameter details, and how this tool relates to siblings, making it incomplete for an agent deciding between list and search tools.

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 compensate. It partially clarifies the sort_by parameter by naming 'volume or liquidity', but it does not enumerate exact accepted values and says nothing about the limit parameter's intended semantics. The compensation is incomplete.

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 action ('List') and the resource ('active Polymarket markets') plus the two sorting options. It is not a tautology and conveys the core function, but it does not explicitly distinguish itself from sibling tools like search_markets or get_markets_by_tag, so it lacks full differentiation.

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 provides no guidance on when to use this tool versus alternatives such as search_markets, get_market, or get_markets_by_tag. It simply states what it does, with no conditions, exclusions, or context to help an agent choose correctly.

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