list_polymarket_events

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states that the tool uses the Gamma API, but fails to mention pagination, rate limits, data freshness, or behavior when no events match. This is insufficient for safe and effective invocation.

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 at two sentences, front-loading the key action and clarification of events. It avoids unnecessary detail. However, it sacrifices some informative context for brevity.

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?

With 6 optional parameters, no output schema, and no annotations, the description is incomplete. It lacks information on return format, example usage, or any constraints like minimum/maximum limit. The conceptual explanation partially compensates but overall leaves significant gaps.

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 covers all 6 parameters with descriptions, achieving 100% coverage. The description adds no parameter-specific meaning beyond the schema; the conceptual explanation of events is helpful but not tied to parameters. Baseline score of 3 is appropriate.

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 action as listing events, explains that events bundle multiple markets, and gives a concrete example (US Presidential Election 2024). This effectively distinguishes it from sibling tools like get_polymarket_event (single event) or search_markets.

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 does not provide explicit guidance on when to use this tool versus alternatives. While the purpose is clear, it lacks instructions on filtering scenarios or when to prefer this over search_markets or get_polymarket_event. The context of optional parameters implies usage but does not directly guide the agent.

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