Update_tracking_number

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

No annotations provided, so description must cover behavioral aspects. Only states a prerequisite (shipment status Shipped) and the update action. Does not disclose idempotency, error handling, authentication requirements, or side effects (e.g., overwriting previous tracking number).

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?

Single sentence that is front-loaded with verb and object. Efficient but could be structured for clarity (e.g., bullet points). No wasted words.

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?

Has output schema, so return values need not be explained. However, for a simple update tool, description should cover parameter usage, conditions, and potential errors. Only the prerequisite is mentioned. Missing details like required vs optional parameters beyond schema and what happens if order not found.

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 has 3 parameters with 33% description coverage. Description adds the shipment status condition for orderNo context, but does not elaborate on trackingNumber or trackingUrl meaning, validation, or format beyond the examples. Does not compensate for low schema coverage.

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?

Describes specific action (update tracking number) for a specific resource (selected order) under a condition (shipment status is Shipped). Clearly distinguishes from sibling tools like Mark_as_ship or Cancel_Order.

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?

States when to use: only when shipment status is Shipped. Implicitly excludes use when status is not Shipped. Does not explicitly mention alternatives or when not to use, but context is clear.

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