polymarket: getPolyMarketEventsByTag

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

Annotations already declare the tool as read-only and idempotent. The description adds no behavioral details such as pagination, rate limits, or that the tagId must come from 'getPolyMarketTags'. It fails to leverage the opportunity to add context beyond annotations.

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 a single, well-structured sentence that communicates the core function without any wasted words. It is appropriately front-loaded.

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's simplicity (2 parameters, no output schema), the description is incomplete. It omits critical context such as the necessity to first call 'getPolyMarketTags' to obtain a valid tagId, and does not mention pagination or result limits. The rich annotations partially compensate, but the description leaves the agent uninformed about key usage details.

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 two parameters, but only 'tagId' has a description referencing another tool. The 'limit' parameter has no description. The tool description does not add any parameter-level meaning, such as the relationship between tagId and the output or the default limit behavior.

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 verb 'Get', the resource 'Polymarket events', and the filtering scope 'by tag/category'. It effectively distinguishes from sibling tools like 'getPolyMarketEvents' (no filter) and 'searchPolyMarketEvents' (keyword search).

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 vs. alternatives. It doesn't mention that 'getPolyMarketEvents' returns all events or that 'searchPolyMarketEvents' is for text-based queries. No exclusions or prerequisites are stated.

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