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

Annotations already cover readOnlyHint and openWorldHint, and the description adds genuinely new behavioral context: the storefront URL is fixed server-side and empty result pages return 200 with an empty array, which preempts a false-negative error interpretation. Auth, rate limits, and return shape are not covered, but the output schema handles the latter.

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?

Purpose and edge-case behavior are front-loaded, then the sibling pointer, then pagination. The main flaw is restating the parameter text already present in the schema, which is redundant padding rather than wasted sentences.

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 an output schema present, return values needn't be described, and annotations carry the safety profile. What remains is adequately covered: what it returns, the empty-page edge case, pagination defaults, and the alternative tool. Complete enough for an agent to call it correctly without opening the 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% and the description repeats the two parameter descriptions ('limit: max collections... default 50, maximum 250' and 'page: 1-based... default 1') near-verbatim. It adds no syntax or behavior beyond the schema, so the baseline 3 is appropriate.

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?

States a specific verb and resource ('Returns normalized collections from Pristine Marketplace') and adds the fixed storefront scope. An agent can immediately tell what this returns and that the source URL is not configurable.

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?

Explicitly routes the agent to pristine_marketplace_collection_products for collection products, which is clear context for a nearby sibling. It stops short of stating when *not* to use this tool or how it differs from pristine_marketplace_products/search.

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