fetchMarketMatches

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

Annotations declare readOnlyHint: true, and the description aligns by describing read-only matching operations. The description adds value beyond annotations by detailing the two modes and filtering capabilities. No contradictions or negative side effects are disclosed, which is acceptable for a read-only tool.

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 concise and front-loaded: a single sentence stating purpose followed by bullet-like mode definitions. Every sentence adds value with no 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?

Given 14 parameters, moderate schema coverage, and no output schema, the description explains modes and key filters but omits details on output format, relation meanings, and confidence thresholds. It is adequate but not fully complete.

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 57%. The description mentions a few key params (query, category, minDifference, sort) but does not add meaning for many others (e.g., market, marketId, relation, minConfidence). It does not compensate fully for the moderate schema coverage.

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 purpose: 'Find the same or related market on other venues.' It defines two distinct modes (Lookup and Browse), making the specific verb+resource clear and differentiating it from sibling tools like fetchMarket or fetchMatchedMarkets.

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 explains when to use each mode (lookup vs browse) and notes supported filtering params. However, it does not explicitly exclude any scenarios or compare to alternatives like fetchMatchedMarkets or fetchRelatedMarkets, which are similar sibling tools.

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