polymarket: getPolyMarketEventsByTag

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

Annotations already provide safety info (readOnlyHint, etc.), but the description adds little behavioral context. It does not describe return format, pagination, ordering, or any side effects, beyond the fact that it filters by tag.

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 sentence with 6 words, highly concise. However, it may be too sparse for effective agent selection, but it is not 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's 2 parameters, no output schema, and many sibling tools, the description is insufficient. It does not explain what 'events' contain, how the tag filter works, or how it differs from searchPolyMarketEvents. Annotations cover safety but not functional completeness.

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 coverage is only 50% (tagId described, limit not). The description does not explain the limit parameter or add any meaning beyond what the schema provides. The tagId description from schema is referenced but not elaborated.

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 filter method 'by tag/category'. This distinguishes it from sibling tools like getPolyMarketEvents (unfiltered) and getPolyMarketTags (tags list).

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 usage when filtering by tag, but does not explicitly state when to use this tool versus alternatives like searchPolyMarketEvents. It lacks guidance on prerequisites (e.g., need tag IDs from getPolyMarketTags) and when not to use it.

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