quote

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

With no annotations provided, the description must disclose side effects, permissions, and behavioral traits on its own. It mentions constraints (1–20 stores/lines) and handle syntax, but doesn't state whether the operation is read-only, modifies anything, or requires special permissions. This is a significant gap.

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 a single sentence with no redundant words. It front-loads the core capacity and then packs in the essential parameter format, making it highly concise and well-structured.

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?

While the tool has an output schema (covering return values), the description omits semantics for two of three parameters ('redetect' and 'destination') and lacks any usage context or alternative tool comparisons. For a tool with three parameters and only core input documented, this is incomplete.

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?

The description provides meaningful detail for the 'quotes' parameter, explaining acceptable values (URL, ref, handle) and the format for multi-variant products. However, it leaves 'redetect' and 'destination' completely unexplained, and with 0% schema description coverage, it only partially compensates for the missing parameter documentation.

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 identifies the specific action of quoting 1–20 stores with 1–20 lines each, which distinguishes it from sibling tools like product, search, and images. However, it doesn't explicitly state the outcome or high-level purpose of a 'quote', leaving some ambiguity for an AI agent.

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?

No guidance is given on when to use this tool versus alternatives like product, search, or images. The description only covers capacity limits and input format, not the appropriate context or conditions for invocation.

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