firestarter_delete_ship_from

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds meaningful behavioral context: deleting the primary location causes quotes to be rated from the platform origin until another location is added or promoted, and only seller accounts can do this. There is 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 a tight two-sentence definition with the core action front-loaded. Every clause carries relevant information: the object, the id format, the consequence, and the authorization scope.

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 one-parameter destructive tool, the description plus annotations cover what is deleted, the side effect on quoting, the auth restriction, and the related save tool. No output schema exists, and the missing details are minor for an agent selecting 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?

The schema covers 100% of parameters with a clear description of location_id including the floc_... pattern. The tool description repeats that pattern and adds the source table name, but does not meaningfully deepen the semantic understanding 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 names a specific verb ('Delete') and resource ('seller ship-from (fulfillment) location'), and pins down the identifier pattern ('floc_...') plus the source table ('firestarter_ship_from_locations'). This clearly separates it from the listing tool and the save/update tool in the sibling set.

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?

It states the operative context ('Seller accounts only') and describes the consequence of deleting the primary location, explicitly pointing to firestarter_save_ship_from as the path to add or promote a replacement. It does not spell out exhaustive when-not-to-use cases, but the guidance is sufficient for this tool.

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