chargebee_retrieve_subscription

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

No annotations are provided, so the description must convey behavior. It specifies the HTTP GET method, which strongly implies a read-only, non-destructive operation. It does not disclose error handling, response format, or access requirements, but the GET method plus 'retrieve' gives a safe profile.

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 and front-loaded with the main action, then includes only the API endpoint and a single parameter explanation. No unnecessary words or redundancy.

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 simplicity (one parameter, output schema exists), the description provides the essential purpose and parameter semantics. Return values are covered by the output schema, so no need to detail them. It lacks explicit usage exclusions, but that is a guidance issue handled in dimension 2.

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 schema has no description for the subscription_id parameter (0% coverage), but the description compensates by explaining it as 'The subscription's unique ID.' This adds meaning beyond the schema's type and title.

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 a subscription (account) by ID' with a specific verb and resource. It distinguishes from siblings like list_subscriptions (list) and cancel_subscription (mutation) by focusing on retrieval of a single subscription.

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?

Usage is implied: use when you have a subscription ID and need its details. However, there is no explicit comparison with alternatives like list_subscriptions or retrieve_customer, nor guidance on when not to use this tool.

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