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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true. The description adds valuable behavioral context: it returns live compatible Shopify choices, missing selections, and the clarification to ask. It also reinforces the open-world behavior by prohibiting inference. No contradiction with annotations.

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 two sentences with zero filler. The core usage instruction is front-loaded, followed by precise behavioral rules, and then the expected return content. Every sentence earns its place.

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 that an output schema exists, this tool's return details do not need to be spelled out. The description covers when to use it, what inputs to pass, what behaviors to avoid, and what the tool returns. Combined with the rich annotations, the agent has all necessary context to select and invoke it correctly.

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 coverage is 100%, and each parameter already has a specific enum and a description stating to include it only when explicitly stated. The description adds a cross-cutting rule that applies to all parameters: never assume, default, recommend, or infer missing values. This goes beyond the schema and clarifies parameter sourcing semantics.

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 a specific verb ('qualify') and resource ('Homebridge fire pit'), and positions the tool for partial, exploratory, or ambiguous requests. It distinguishes itself from the likely configuration sibling by emphasizing qualification rather than exact configuration. The purpose is unmistakable.

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 explicitly says to use the tool for 'every partial, exploratory, or ambiguous Homebridge fire-pit request' and gives strong directives about only passing explicitly stated selections and never inferring missing attributes. It does not explicitly name the alternative configuration tool, but the 'before exact configuration' phrase implies the next step clearly enough.

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