tiendanube_get_customer

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

The description details what the tool returns (personal details, contact info, addresses, etc.) and notes it retrieves a single customer. As annotations are absent, the description carries the burden; it implies a read-only operation but does not explicitly state that. It lacks info on error conditions or permissions, but for a simple GET this is mostly sufficient.

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 clear header and bullet-style list of fields. It front-loads the purpose and usage, with no extraneous information. Every sentence adds value, making it easy for an agent to parse quickly.

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?

The description lists the types of data returned but does not explain the response structure or format, especially since there is no output schema. For a single-customer retrieval tool, this is largely complete, but a brief note on the response shape would enhance 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?

The input schema covers both parameters (customer_id and fields) with 100% description coverage. The tool description does not add additional meaning or examples beyond what the schema already provides. Since schema coverage is high, a baseline score of 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 'Retrieve complete details for a single customer by their unique ID', specifying the verb and resource. Its title 'GET SPECIFIC CUSTOMER' and the mention of listing fields (personal details, contact info, addresses, etc.) distinguish it from sibling tools like tiendanube_list_customers and tiendanube_search_customers.

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 provides context: 'Use this when you need comprehensive customer information... Essential for customer service, account management, and personalized marketing.' It implies when to use but does not explicitly exclude scenarios or name alternative tools for listing or searching. The context is clear but could be more directive.

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