tiendanube_get_order_transaction

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

The description is minimal for a tool with no annotations. It discloses that the operation is a retrieval (read-only), but does not mention error handling (e.g., if order or transaction not found), authorization requirements, or any side effects. For a simple get, this is adequate but not rich.

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 a single sentence, free of fluff, and directly conveys the tool's purpose. It is appropriately sized for the tool's simplicity.

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 tool's straightforward nature (2 parameters, no output schema, no nested objects), the description covers the essential action and inputs. However, it could be more complete by mentioning the return type (e.g., 'returns the transaction object') or error cases, but overall it is sufficient.

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 both parameters described ('Order ID', 'Transaction ID'). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 action ('Retrieve') and the resource ('a single transaction'), and specifies the unique identification method ('by order and transaction IDs'). This distinguishes it from sibling tools like tiendanube_list_order_transactions, which retrieves multiple transactions.

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 when a specific transaction is needed, but does not explicitly state when to use this tool over alternatives (e.g., when to use tiendanube_list_order_transactions instead) or any conditions or prerequisites. No exclusion criteria are provided.

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