store_delete_shipping_rate

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

Annotations already declare destructiveHint=true and idempotentHint=true, which cover the key behavioral traits. However, the description adds no additional context beyond repeating the action. It does not mention that deletion is permanent, that it affects only the specified rate, or any side effects. Since the description adds no value beyond what annotations already provide, the score is low.

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 extremely concise—a single phrase with no extraneous words. It is well-structured in the sense of being brief and to the point. However, it is so sparse that it might be considered under-specification rather than efficient writing, but given the tool's simple nature, it earns a pass for conciseness.

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 destructive operation with two required parameters and no output schema, the description is incomplete. It does not explain what happens on success (e.g., returns success/failure), whether the rate must exist first, or any consequences of deletion. The annotations cover destructiveness, but the description lacks the necessary contextual detail for an agent to confidently invoke this 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 input schema fully documents each parameter. The description itself adds no parameter information. With high coverage, the baseline is 3 because the schema carries the burden. The description does not compensate or clarify anything 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 'Delete shipping rate' clearly states the action (delete) and the resource (shipping rate). It is specific enough to convey the core purpose, though it does not differentiate from sibling operations like store_delete_shipping_zone or store_update_shipping_rate. It adds no detail about the context (e.g., within a shipping zone), but the verb+resource pairing is unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, conditions, or exclusions. With many sibling store tools, there is no differentiation to help an agent decide between delete, update, or list operations. This is a complete absence of usage guidance.

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