polymarket: getPolyMarketEvents

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

Annotations already indicate read-only and idempotent behavior. The description adds 'Returns compacted data optimized for efficiency,' which provides some behavioral context beyond annotations. However, it does not disclose pagination or other traits like sorting defaults.

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 very short: two sentences. The first sentence states the purpose clearly; the second adds minor efficiency info. It is concise but could be more structured with additional details without becoming verbose.

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 tool has 6 parameters and no output schema, the description is incomplete. It does not explain pagination (limit/offset), sorting (order/ascending), filtering (tag_id, featured), or when to use sibling tools. The 'compacted' note is vague.

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 only 33% (only limit and tag_id have descriptions). The description does not explain any parameters, failing to compensate for low schema coverage. Users must infer meaning from parameter names and defaults.

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 returns a list of Polymarket events, which is a specific verb and resource. However, it does not explicitly differentiate from sibling tools like getPolyMarketEvent (single event) or getPolyMarketEventsByTag (filtered by tag), though the name implies it.

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?

No guidance on when to use this tool versus alternatives such as getPolyMarketEventsByTag or getPolyMarketEvent. The description lacks context about when it is appropriate or when to avoid it.

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