tiendanube_get_cart

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool returns 'items, totals and metadata' without discussing side effects, permissions, rate limits, or behavior when both cart_id and cart_token are provided. The nature may be inferred as read-only, but explicit behavioral traits are missing.

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 with a prominent 'GET CART' label followed by concise details. Every word is informative with no redundancy, and it front-loads the core action efficiently.

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 absence of an output schema and annotations, the description adequately covers the tool's purpose, identification methods, and return summary. It lacks specifics on required fields (none set as required) and error scenarios, but for a simple retrieval tool, it provides sufficient baseline completeness.

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?

Although schema coverage is 100%, the description adds valuable context by stating that the cart can be retrieved 'by numeric id or token', clarifying the alternative identification role of cart_id and cart_token. This goes beyond the individual parameter descriptions in the schema, aiding parameter selection.

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 explicitly states the action ('GET CART - Retrieve') and the resource ('shopping cart') with specific identification methods ('by numeric id or token'). It differentiates from sibling tools like tiendanube_add_cart_item or tiendanube_clear_cart, clearly defining its scope.

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 retrieving a cart, but does not explicitly contrast with alternatives like tiendanube_get_checkout or tiendanube_get_abandoned_checkout. No guidance is provided on prerequisites, error handling, or when to use this tool over others, leaving the agent to infer context from the name and siblings.

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