firestarter_track_order

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

With readOnlyHint=true and destructiveHint=false from annotations, the safety profile is already known. The description adds useful behavioral context: prerequisite state (paid and shipped), what data is returned, and the limitation to shipped orders. It stops short of describing error cases or pagination, but that's acceptable for a simple read-only tracking tool.

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?

Three sentences: purpose and outputs, usage trigger, constraint with alternative. Every sentence adds value; no filler or repetition. Front-loaded with the core action.

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?

Despite having no output schema, the description enumerates the key return fields (carrier, tracking number, estimated delivery, location/events). With a single required parameter and complete schema coverage, this is all the context an agent needs to select and invoke the tool correctly.

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 description coverage is 100% for the only parameter (execution_id). The description does not add any parameter-specific details beyond what the schema already notes, so the baseline of 3 applies. There is no gap to compensate for.

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 opens with a specific verb and resource: 'Track a shipped order's delivery status.' It lists concrete outputs (carrier, tracking number, estimated delivery, events) and explicitly distinguishes this tool from firestarter_status for unpaid/unshipped orders. This makes the purpose unmistakable and differentiates it from siblings.

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 usage triggers ('when a buyer asks where's my order?') and a clear exclusion: 'Only works after an order has been paid and shipped — for unpaid/unshipped orders, use firestarter_status instead.' This provides both when-to-use and when-not-to-use, naming the specific alternative.

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