firestarter_delete_ship_from

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

Annotations already mark this as destructive, but the description adds critical behavioral context: what happens if the primary location is deleted, and the fallback behavior. It also clarifies the scope (seller accounts only), which goes beyond the annotation hints. No contradictions 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 three sentences: the first states the core action, the second explains the primary-deletion consequence and alternative, and the third sets the account scope. Every sentence adds value, and the most important information is front-loaded.

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 delete operation, the description covers the essential context: what is deleted, the fallback behavior if the primary is removed, and the account restriction. The sibling tool list provides further context, and no output schema is needed.

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 the single parameter with a description, and the tool description adds the id format (floc_) and the source table (firestarter_ship_from_locations). This provides useful context beyond the schema's basic description.

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 uses a specific verb ('Delete') and resource ('seller ship-from location by id'), clearly distinguishes from sibling tools like firestarter_save_ship_from, and includes the id format (floc_...). This leaves no ambiguity about the tool's function.

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 gives explicit context for when to use the tool (deleting a ship-from location), and provides an alternative action if the primary is deleted (use firestarter_save_ship_from to promote another). It also states the consequence of not doing so (quotes fall back to platform origin) and the account prerequisite (seller accounts only).

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