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

No annotations are provided, so the description carries the full burden. It does disclose the meaningful behavioral fact that the output is a series of snapshots over time rather than a single value, but it omits anything about snapshot granularity, pagination/truncation behavior when limit is hit, or what happens if the window exceeds available data.

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?

A single front-loaded sentence with no filler, hedging, or repeated schema content. Every word carries information and the key qualifier ('historical ... over time') arrives immediately.

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?

The tool is simple (4 params, 1 required, no nesting) and the schema is fully described, but with no output schema and no annotations the description should at least sketch the return shape (e.g. timestamp/price pairs) and snapshot granularity. It gestures at the return ('snapshots over time') without enough detail for an agent to plan parsing or pagination.

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 slug, hours, limit, and notification_message are already documented with defaults and maxima. The description adds nothing beyond that (no guidance on sensible hour/limit combinations or the relationship between window and snapshot density), so the baseline 3 applies.

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 states a specific verb and resource ('Returns historical YES price / implied probability snapshots') for a named domain (Polymarket market), which is far more specific than a bare name restatement. It implicitly distinguishes itself from the current-odds sibling by emphasizing 'historical ... over time', but never names that sibling explicitly.

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 only implied: the word 'historical' suggests this is for time-series analysis rather than current pricing, which a reader can infer against get_market_odds. There is no explicit when-to-use, when-not-to-use, or named alternative, and no prerequisite guidance such as needing a valid slug.

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