delete_shipping_profile

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is known. The description adds the 'local' qualifier, indicating only locally saved profiles are impacted, which is useful context beyond the annotations. However, it does not state whether the deletion is irreversible, what happens when the profile name does not exist, or whether in-use profiles can be deleted.

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 and front-loads the core operation in one sentence. The following Args block duplicates the schema's parameter description verbatim, which is mildly redundant, but overall there is little wasted text.

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?

This is a simple single-parameter mutation tool with no output schema, so the description covers the essentials. It omits the post-condition behavior an agent would want before invoking a destructive tool: confirmation of success, behavior on missing names, and whether the removal is recoverable.

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%, and the description's Args section restates the same text as the schema ('Profile name to delete'), adding no new meaning such as case sensitivity, exact-match behavior, or error conditions. With full schema coverage the baseline of 3 applies.

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 gives a specific verb and resource: 'Delete a saved local shipping profile.' It clearly distinguishes the operation from siblings like list_shipping_profiles or save_shipping_profile, though it doesn't name them explicitly. The word 'local' adds useful scope information about which profile store is affected.

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?

There is no explicit guidance on when to use this tool versus alternatives, and no prerequisites are stated. An agent must infer usage from the name alone; the description never mentions that save_shipping_profile and list_shipping_profiles are related siblings, nor does it describe conditions where deletion is appropriate or inappropriate.

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