tiendanube_reopen_order

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

No annotations provided, so description must carry the burden. Only states 'reopen' without disclosing side effects, permissions, or consequences (e.g., impact on inventory, payments, or whether it reverses closure).

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?

Extremely concise with two short phrases. Front-loaded capital 'REOPEN ORDER' signals purpose quickly. Minor redundancy ('REOPEN ORDER' and 'Reopen...') but no filler.

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 mutation tool with no annotations and no output schema, the description is too sparse. Does not explain reopening behavior, error conditions, or what the agent should expect after invocation.

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?

Parameter 'order_id' is fully described in schema (100% coverage). Description adds no additional meaning beyond the schema's 'Order ID'.

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?

Clearly states verb 'Reopen' and resource 'order', with explicit scope 'previously closed'. Distinguishes from sibling tools like 'close_order' and '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?

No guidance on when to use vs. alternatives (e.g., when an order is cancelled vs. closed). Does not mention prerequisites like order must be in closed state.

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