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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description adds no behavioral context beyond what annotations provide—no mention of side effects, reversibility, or consequences. It only restates the action without disclosing any additional traits.

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 short but redundant, repeating the same sentence twice ('Updates the name of a variant option. Guidance: Updates the name of a variant option.'). The 'Guidance:' section is filler and not front-loaded effectively. It could be a single concise sentence.

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?

For a simple 2-parameter update tool with no output schema, the description should still explain what happens after the update, any prerequisites, or return behavior. None of that is provided. Annotations cover safety, but the description leaves the agent without enough context to confidently call the tool.

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 baseline is 3. The description lists 'option_id, name' as context but adds no extra meaning beyond the schema's own parameter descriptions. It neither clarifies formatting nor adds constraints.

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 the tool updates the name of a variant option, specifying the verb and resource. It is specific enough to distinguish from many sibling tools like shop_update_variant, but it doesn't explicitly differentiate from other option-related tools (e.g., shop_create_option, shop_delete_option) or clarify scope.

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. It does not mention prerequisites, typical scenarios, or exclusions. The agent must infer usage from the name and schema alone.

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