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

With no annotations, the description carries the full burden, and it partially does: it discloses that results are paginated and include prices, volume, and status. It omits whether authentication is required, whether closed/settled markets are included by default, and any rate-limit or ordering behavior, so the safety and result-set profile remain unclear.

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?

Two sentences, front-loaded with the action and resource, then the return shape. No filler, though it is quite terse for a five-parameter discovery tool.

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 no output schema and no annotations, the description must compensate more, and it only briefly sketches the return payload and pagination. Default status scoping, sort order, and auth expectations are unaddressed, leaving gaps an agent would need to resolve before calling it confidently.

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 60%, and the description only echoes the q and category concepts and mentions pagination generally. It adds nothing about the status enum values or cursor semantics, and its use of 'status' as a returned field can be confused with the status filter parameter.

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?

Names a specific verb (Search) and resource (PredictAsiaX markets) plus the two primary filter modes, keyword and category. An agent can distinguish it from pax.market_get (single market) and pax.category_list, but the description never names those siblings, so the differentiation is inferred rather than stated.

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 phrase 'by keyword or category' implies when this tool is relevant versus a direct lookup, but there is no explicit when-to-use/when-not, no note that it is the discovery entry point versus pax.markets_top_volume or pax.probability_movers, and no mention of default filtering behavior. Usage is only implied.

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