polymarket_series_list

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

With no annotations, the description must disclose behaviors but only lists return fields. No mention of authentication, rate limits, or side effects. The read-only nature is implied but not explicit.

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 concise with two sentences, front-loading the purpose and hierarchy. The return type is clearly specified. However, it lacks structure (e.g., separate sections for purpose, params, returns).

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 6 undocumented parameters and no output schema or annotations, the description is incomplete. It does not cover filtering, pagination, ordering, or behavior, leaving an agent without sufficient guidance.

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 description provides no explanations for the six parameters (slug, limit, order, closed, offset, ascending). Schema coverage is 0%, so the description fails to add meaning beyond the schema field names.

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 'Series catalogue' and explains the hierarchy ('top of Gamma's series → events → markets hierarchy'). It defines what a series is and distinguishes this list tool from the singular polymarket_series tool by indicating it returns a catalogue.

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 this tool is for browsing all series, but does not explicitly state when to use it over siblings like polymarket_series (for a specific series) or polymarket_events (for events). No usage context or exclusions provided.

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