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

No annotations are provided, so the description carries the full burden. It does disclose domain-meaningful behavior for downstream use (null = not answered, matchable=false means the task list is unconfirmed and thus not searchable or quotable, payment is 'declared' and paid directly), but says nothing about read-only status, permissions, error cases for a bad slug, or rate limits.

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?

A single ~200-word sentence with deeply nested parentheticals ('packages: each package with its price, limits, kinds and the tasks it includes...') that is hard to parse. The purpose is front-loaded, but the remainder is a wall of field documentation with no structure.

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, the description does the heavy lifting of documenting the returned payload, including nested services, pricing_model, add-ons, area and takes semantics, so return-value coverage is unusually thorough. However it omits the parameter's meaning, when to call it, and any failure behavior, leaving real gaps for an agent.

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 0% for the single parameter merchant_slug, and the description never explains it - no format, no source, no example. It only implies 'one merchant' is identified, which is weaker than what the schema alone conveys.

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 opening clause 'Describe one merchant' gives a specific verb (describe) and a bounded resource (one merchant), which is distinguishable from siblings like search, quote and taxonomy that operate over sets or pricing. The purpose is clear despite being buried under a very long run-on payload listing, and there is no explicit sibling differentiation beyond the singular 'one merchant'.

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?

There is no statement of when to use this tool versus search, taxonomy or quote, and no prerequisites such as where merchant_slug comes from. Usage is only implied by the singular 'one merchant', leaving the agent to infer the routing.

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