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

With no annotations, the description carries the full disclosure burden. It does reveal the returned fields (outcomes, dates, volumes), but 'recently' is undefined, and it says nothing about ordering, default date window, pagination, or whether the 2-param schema's negative days_back values are meaningful.

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, and the resource is stated immediately. Its brevity is efficient, though partly at the cost of the missing usage and parameter detail noted elsewhere.

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?

This is a 2-parameter data-retrieval tool with no annotations, no output schema, and 0% parameter coverage, yet the description is one sentence. Defaults, sort order, and what the limit and days_back actually control are all absent.

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 0%, so the description would need to compensate, but neither 'limit' nor 'days_back' is explained in it. 'Recently' loosely gestures at a date window but gives no default, units, or handling of the negative values the schema permits.

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 resource and scope: recently resolved Polymarket markets with final outcomes, resolution dates, and volumes. It is clearly distinct in content from scanning tools like polymarket_market_scan, though it never explicitly names those siblings as alternatives.

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?

There is no explicit when-to-use guidance, no prerequisites, and no pointer to alternative tools like polymarket_market_scan or trending_markets. The intended use is only implied by the phrase 'recently resolved.'

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