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

There are no annotations, so the description must disclose behavioral traits. It only states 'Find markets' without explaining query behavior, pagination, result format, or any side effects. The agent cannot infer whether this is a safe read-only operation or what the response will look like.

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 one short sentence and completely free of fluff. It is front-loaded with the primary purpose and can be read in under two seconds. Every word earns 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?

With 11 parameters, no annotations, and no output schema, this description is insufficient. It does not explain return values, default behavior, or context for using the numerous filters. A tool this complex requires more context to be safely invoked.

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?

The input schema covers all parameters with descriptions, so the baseline is 3. The description adds no extra meaning beyond saying 'various filters', which is already evident from the schema. It repeats the idea of filters but does not elaborate on parameter syntax or relationships.

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 clearly states the tool's action ('Find markets on Polymarket') and the resource ('markets'), with a specific scope ('using various filters including the ability to search'). It is a specific verb+resource statement, but it does not differentiate from siblings like dome_markets_get or search_markets.

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 description provides no guidance on when to use this tool versus alternatives such as search_markets or dome_markets_get. It does not mention any exclusions or prerequisites, so the agent is left without context for choosing among sibling tools.

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