get_polymarket_event

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

No annotations are provided, so the description must carry the full burden. It states the tool 'gets' data, but does not disclose behavioral traits such as whether the eventId can be a slug, the structure of the returned markets, data freshness, or any side effects. The description adds minimal value beyond the tool name.

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 concise: two sentences, front-loaded with the core purpose, and the second sentence provides essential context about what an event is. No extraneous words or repetition.

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 lack of output schema and annotations, the description is adequate but not comprehensive. It explains that the event comes 'with all its associated markets,' but does not specify the format or structure of those markets. For a tool with many siblings, more detail on what 'associated markets' entails would improve 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?

The input schema describes the only parameter 'eventId' as 'Event ID or slug' with 100% coverage. The description offers no additional meaning beyond the schema, so the baseline score of 3 is appropriate. No extra value is added.

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's purpose: 'Get a single Polymarket event with all its associated markets.' It specifies the resource (event) and the action (get), and differentiates from sibling tools like list_polymarket_events (which lists multiple events) and get_market_* (which targets individual markets).

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 the tool is for retrieving a single event, but it does not provide explicit guidance on when to use it versus alternatives such as list_polymarket_events or get_market_info. No when-not-to-use or exclusion criteria are given, leaving the agent to infer usage from the name and brief description.

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