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

Although readOnlyHint=true already establishes safety, the description adds substantial behavioral context: it names the four possible verdict branches, the resolution basis categories, UMA dispute state, rule-wording risks, executability checks, caching, and heuristic limitations. This goes well beyond the annotation.

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 front-loaded with purpose and output, then cleanly separated into 'Use when,' 'Limitations,' and 'Alternatives.' Every section adds useful routing or constraint information without redundancy.

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 read-only assessment tool with an output schema already present, the description provides the necessary usage conditions, output categories, caching behavior, limitations, and alternatives. An agent has enough context to invoke it correctly without reading the output schema.

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% for the single 'market' parameter, which already documents the accepted slug, numeric id, and URL formats. The description adds no further parameter-level syntax or constraints beyond saying it accepts one Polymarket market.

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: 'Return a decision-ready resolution-risk verdict for one Polymarket market.' It also distinguishes the tool from alternatives like web_search and http_fetch, and its scope is clear from the opening sentence.

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 'Use when' section explicitly tells the agent to call once per market before placing, quoting, or forecasting a Polymarket position. It names alternatives (web_search, http_fetch) and documents caching behavior for repeat calls within two minutes.

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