polymarket_events

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

The description notes that the data is 'credential-free public' implying no authentication needed, and describes the source. However, with no annotations, it does not disclose rate limits, pagination behavior beyond schema, or other traits like idempotency. Some context is added but incomplete.

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?

Two sentences, front-loaded with purpose, no redundant information. Concise and efficient.

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?

The tool has no output schema and a moderate number of parameters (5). The description only vaguely mentions 'normalized event rows' without detailing what fields are returned. This leaves agents guessing about the output structure, which is critical for a listing tool.

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?

All five parameters have descriptions in the input schema (100% coverage). The description adds no extra meaning beyond what the schema already provides, so baseline 3 applies.

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 tool lists Polymarket events and specifies the data source (Gamma events JSON). It distinguishes itself from sibling tools like polymarket_event_detail or polymarket_events_similar by focusing on listing all events.

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 siblings such as polymarket_event_detail or polymarket_events_similar. An agent would need to infer usage from the name alone.

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