tiendanube_get_order_fulfillment

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

With no annotations, the description carries full burden for behavioral disclosure. It only indicates a read operation ('Retrieve'), but fails to mention specific behavioral traits such as permissions, rate limits, or response structure. For a safe read tool, more explicit transparency is needed.

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 concise, using a single paragraph with a clear leading statement. It includes an emoji and bold for quick scanning. Slightly better front-loading could be achieved, but overall very efficient.

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 single parameter and no output schema, the description lists expected return fields (tracking numbers, carrier info, etc.) and use cases. It adequately covers the tool's purpose and typical data, though it could mention behavior for orders without fulfillment.

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 100% with 'order_id' having a description. The description adds no additional parameter meaning beyond the schema, so baseline score of 3 applies.

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 verb 'Retrieve' and specific resource 'detailed fulfillment and shipping information for a specific order', listing concrete data points. It distinctly separates from siblings like 'get_fulfillment_order' by focusing on order-level fulfillment.

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 implies usage for 'logistics management, customer support, and shipping status updates', but does not explicitly state when not to use or compare to alternatives like 'get_fulfillment_order' or 'list_fulfillment_orders'. Usage guidance is present but incomplete.

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