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

Annotations already declare readOnlyHint and openWorldHint, and the description adds important behavioral context beyond them: the cost is $0.02 per comparison, only one product is sampled per store, and unavailable evidence remains unknown. These details materially affect whether and how an agent should invoke the 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 front-loaded with the tool's purpose, then adds cost, appropriate-use routing, and a sampling caveat. Every sentence contributes operational information without repetition or filler.

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 the full schema coverage, existing output schema, and annotations covering read-only and open-world behavior, the description is complete enough to call the tool correctly. It covers output dimensions indirectly, sampling limitations, cost, and alternative tools.

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%, so the schema already documents the domain, competitor_domains, and context parameters thoroughly. The description reinforces that competitors are capped at three and that one product is sampled per store, but it does not add syntax or constraints beyond the schema.

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 states a specific verb and resource: it compares a brand against up to three competitor store domains as a shopping schema covering prices, ratings, availability, shipping, and returns. It also distinguishes itself from named sibling tools, so an agent can identify its role without opening schemas.

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?

It explicitly says to use this tool for a bounded cross-store comparison and names alternatives: universal_product_url_to_json for one product and muse_agentic_store_readiness_auditor for a single-store discovery audit. This gives clear when-to-use and when-to-use-something-else guidance.

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