firestarter_ship_from_locations

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context beyond this: the PRIMARY location drives all shipping quote ratings, and this is the first place to check for shipping display issues. The 'Seller accounts only' note also adds access-related behavior not present in the 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, each serving a distinct purpose: what the tool does, why the primary location matters and when to use, and how to modify locations plus account scope. No waste, and the key verb 'List' appears at the start.

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, parameterless list tool with strong annotations and no output schema, the description covers the essential purpose, the importance of the primary location, troubleshooting context, modification alternatives, and eligibility. This is sufficiently complete for effective selection and invocation.

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 input schema has no parameters, and the baseline for 0-parameter tools is 4. The description adds semantic meaning by explaining what 'ship-from locations' are and the significance of the PRIMARY location, providing value beyond the empty 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 clearly states the tool lists the seller's ship-from (fulfillment) locations, using a specific verb and resource. It also distinguishes itself from the related firestarter_save_ship_from and firestarter_delete_ship_from tools by framing this as the listing operation.

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?

Provides explicit guidance on when to use this tool: when buyers see incorrect shipping prices or 'can't ship there' messages, check this first. It also names alternatives for adding/correcting (firestarter_save_ship_from) and removing (firestarter_delete_ship_from), and restricts usage to seller accounts.

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