firestarter_save_ship_from

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

Beyond the readOnlyHint=false and destructiveHint=false annotations, the description discloses important behavioral traits: the primary location drives every quote's origin, and it distinguishes create vs. update vs. promote side effects. It also notes the seller-only restriction, adding access-control context. 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 single well-structured paragraph with numbered forms, making it easy to parse. Every sentence carries necessary information, and the front-loaded action statement quickly communicates the tool's purpose. No filler or redundant content.

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?

Given the tool's complexity (10 parameters, no output schema), the description covers the critical usage logic: the three forms, required fields, and the primary-origin effect. The main gap is the lack of return-value/error information, which is not compensated by an output schema, but the core behavior is well defined.

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?

Although schema coverage is 100%, the description adds value by explaining conditional parameter requirements (e.g., street1 and city required when creating; state/zip required for US/CA/AU origins). It clarifies the role of location_id in the three forms, which the schema alone does not convey.

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 specifies the verb 'Add or update' and the resource 'seller ship-from (fulfillment) location', and immediately explains the purpose ('address shipping rates are quoted FROM'). It distinguishes itself from siblings like delete_ship_from and ship_from_locations by covering create/update/promote functionality, making the tool's scope 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 clear usage context by enumerating three distinct forms (create, update, promote) with specific conditions for each, and adds a constraint ('Seller accounts only'). It does not explicitly name alternatives or when-not-to-use cases, but the form-based guidance effectively tells the agent how to invoke the tool correctly.

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