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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no indication of what the rewards data includes, freshness, or rate/auth behavior, and it does not contradict the annotations.

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?

It is short, but this is under-specification rather than conciseness - a single four-word fragment that carries almost no information. Brevity here does not earn its place.

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?

An output schema exists so return values need not be spelled out, and annotations cover read-only safety. Still, for a detail-lookup tool in a crowded Polymarket family, the description leaves the agent unable to confirm what 'rewards market' detail means or when to prefer it over nearby alternatives.

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% and the single condition_id parameter is documented in the schema itself. Per the coverage rule the baseline is 3; the description adds no format hints or examples beyond what the schema already provides.

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 is a noun fragment that largely restates the tool name ('polymarket_rewards_market' -> 'Polymarket rewards market detail'). It implies retrieval of a rewards market's detail, but supplies no verb and does not distinguish itself from siblings like polymarket_rewards_markets (plural) or polymarket_market_detail.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives, despite a dense sibling set (polymarket_market_detail, polymarket_rewards_markets, polymarket_markets). The agent must infer everything from the name.

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