chargebee_retrieve_customer

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

With no annotations provided, the description must convey behavioral traits. It explicitly states this is a GET operation, signaling a safe read. It does not detail error cases, authentication, or return format, but for a simple retrieval the GET disclosure is a minimal yet adequate transparency step.

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 extremely concise with zero wasted words. It includes the API endpoint, a single argument definition, and nothing else. Perfectly front-loaded and easy to scan.

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 simple single-parameter retrieve tool with an output schema, the description covers the essential purpose and parameter. It doesn't explain return values, but the output schema handles that. The API endpoint adds useful context. It would benefit from noting possible errors, but overall complete for its simplicity.

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 0%, so the description must compensate. It describes customer_id as 'The customer's unique ID', which adds meaning beyond the schema's bare 'Customer Id' label. However, this is still minimal; it doesn't clarify formats, examples, or how to find the 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?

The description clearly states the tool retrieves a customer by ID, using the specific verb 'Retrieve' and resource 'customer'. It distinguishes itself from siblings like list, create, and update 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 clearly implies use when you have a customer ID and need that specific customer's details. It doesn't explicitly mention alternatives, but the singular 'by ID' naturally contrasts with listing or creating. The API endpoint reinforces the targeted retrieval context.

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