update_fulfillment_tracking

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

With no annotations, the description reveals key behaviors: Shopify auto-derives URL for known carriers, omitted fields unchanged, notifyCustomer triggers email. Lacks mention of idempotency or permissions, but covers main traits.

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?

Two sentences: first states purpose, second provides usage and parameter semantics. No filler; every sentence adds value.

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?

Covers all parameters and key behaviors. Does not describe return value or error conditions, but no output schema exists; given complexity, this is mostly complete.

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 coverage is only 20%, but description adds meaning: company+number suffice, URL auto-derived, notifyCustomer controls re-sending. This compensates for sparse schema descriptions.

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 action ('Update or add tracking info on an existing fulfillment') and distinguishes from sibling tools like create_fulfillment and cancel_fulfillment by specifying it is for after-the-fact corrections.

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?

Explicitly tells when to use: after create_fulfillment without tracking, or when fixing a wrong tracking number. Provides guidance on parameters (company+number sufficient) and optional notifyCustomer behavior.

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