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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not clarify whether the list is live or cached, whether pagination or limits apply, what data each market item contains, or whether it is a read-only operation.

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 extremely short and free of filler, but it is under-specified rather than efficiently complete. It lacks a clear verb phrase like 'Fetch' or 'Return', and it does not structure the description to include scope, output, or usage context.

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 large sibling set including many Polymarket-related tools, no output schema, and no annotations, this description is inadequate. An agent cannot determine what list is returned, what the entries look like, or how this differs from polymarket-odds, poly-volume, or polymarket-scan.

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 tool has zero parameters and schema coverage is 100%, so there is no parameter documentation burden on the description. The baseline of 4 applies because no parameter explanation is needed.

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 states a specific resource ('Polymarket markets list') and an implied action (list), so it is not merely a tautology. However, it does not specify what fields or filtering are offered, nor does it distinguish itself from several similar Polymarket-related siblings such as polymarket-odds, poly-depth, or polymarket-scan.

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 guidance on when to use this tool versus the many other Polymarket/poly tools. With siblings like polymarket, poly-price, poly-volume, poly-signals, and polymarket-odds, the absence of any routing or context leaves the agent to guess which tool is appropriate.

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