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

No annotations are provided, so the description carries the full behavioral burden. It makes clear that the tool retrieves data and lists the returned fields, but it does not state error behavior, authentication needs, rate limits, or any explicit read-only/side-effect profile.

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 definition is a single front-loaded sentence that states the resource, key returned fields, and scoping parameter without any wasted phrasing.

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?

For a simple lookup tool with a fully described schema, the description is largely complete: it covers the required slug input and, since there is no output schema, lists the key returned fields. It still omits explicit usage guidance versus siblings and behavioral details such as failure modes.

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 100%, so both parameters are already documented in the input schema. The description reinforces the required "slug" parameter with "by slug" but adds no additional semantics for the optional notification_message parameter; baseline 3 is appropriate.

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 uses a specific verb ("Returns") and resource ("current prices, implied probability, volume, liquidity, and metadata") scoped to "a specific Polymarket market by slug." This is clear enough to distinguish it from general market search or orderbook tools, though it does not explicitly name any sibling alternative.

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?

Usage is implied by the phrase "specific Polymarket market by slug" and by the odds-oriented return fields, suggesting this is the tool to call when you already have a market slug and need pricing/probability data. However, there is no explicit guidance on when to use this versus get_market_summary, get_market_orderbook, or search_markets.

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