Get subscription with addons

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: 'Get' implies a read, but it never states that it is read-only/non-mutating, what permissions or reseller context are required, or what happens if the account has no subscription. For a tool with zero annotation coverage this is a significant gap.

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?

A single short sentence with the key scope ('one subscription including addons') front-loaded and no filler. It is efficient, though its brevity comes partly from saying little of substance.

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 two-parameter read tool with full schema coverage, the description is minimally viable. But with no annotations and no output schema, the phrase 'full detail' is left undefined - the agent cannot tell what fields or addon data come back, which is the main open question.

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 description coverage is 100%, so both accountId ('ALSO Cloud Account ID') and resellerContext are already documented in the schema. The description adds no syntax, default, or behavioral meaning beyond that, so the baseline 3 applies.

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 states a verb and resource ('full detail for one subscription'), and the phrase 'including addons' hints at what separates it from the sibling get_subscription. However, it mostly restates the tool name/title and never explicitly contrasts itself with get_subscription or get_subscriptions, so an agent must infer the distinction.

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?

There is no when-to-use guidance, no prerequisite (e.g., needing an existing subscription ID or account context), and no named alternative. With sibling tools like get_subscription and get_subscriptions in scope, the agent gets no routing help at all.

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