polymarket: getPolyMarketEvent

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the description does not need to repeat safety. It adds 'detailed info' but does not elaborate on what fields are returned or any behavioral traits beyond the annotations. With annotations covering the main concerns, the description is adequate but not rich.

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 10 words, front-loading the verb 'Get' and efficiently conveying the purpose. Every word earns its place; there is no redundancy or unnecessary detail.

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 (1 parameter, no output schema, but rich annotations), the description is complete enough for an agent to understand its purpose and usage. It could optionally mention the output type, but the lack is not critical due to the straightforward nature of the 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?

The input schema has 100% coverage for the single 'slug' parameter, with a description 'Event slug (from event.slug)'. The tool description only mentions 'by slug' without adding new semantics. As per guidelines, high schema coverage warrants a baseline of 3, and the description does not improve upon it.

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 'Get detailed info for a specific Polymarket event by slug', which specifies the verb (Get), resource (Polymarket event), and identifier (slug). It distinguishes from siblings like getPolyMarketEvents (list events) and searchPolyMarketEvents (search), making the tool's purpose unambiguous.

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 a specific event slug is known, but it does not explicitly state when to use this tool versus alternatives (e.g., getPolyMarketEvents for listing, searchPolyMarketEvents for fuzzy search). No exclusions or prerequisites are provided, leaving usage context implied rather than explicit.

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