track_shipment

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the external dependency (Nova Poshta) and implies a sync/fetch against that provider, but says nothing about whether it mutates local order state, what happens for an unknown order ID, error behavior, or any auth/rate constraints.

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?

A single tight sentence with the action and the source system front-loaded and no filler. It is efficient, though the compression comes at the cost of the missing guidance noted elsewhere.

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 one-parameter, non-nested tool with no output schema, the description states the input key, the data source, and the shape of what is returned (checkpoints plus delivery status), which is what an agent needs to call it correctly. The only real gap is the undocumented sync/mutation behavior.

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% and the single parameter is fully documented in the schema, so the baseline is 3. The description's 'by order ID' adds no syntax, format, or edge-case detail beyond the schema's 'Unique numeric ID of the shipped order'.

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 gives a concrete verb pair ('Synchronize and retrieve') plus a specific resource ('live parcel checkpoints and delivery status') scoped to a named provider and input key ('from Nova Poshta by order ID'). It is clearly distinguishable from generic order tools, though it never explicitly contrasts itself with the nearest siblings such as get_order_details or create_nova_poshta_waybill.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent cannot tell from the text whether to reach for this versus get_order_details, print_waybill, or create_nova_poshta_waybill for a given delivery question.

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