Retrieve Subscription

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

The description aligns with the annotation 'readOnlyHint: true' but adds no further behavioral details (e.g., what fields are returned, if any filtering applies). Since annotations already cover safety, no extra context is provided.

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, front-loaded sentence with no filler. Every word is necessary and earned its place.

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 a single parameter, annotations, and many sibling tools, the description is functional but minimal. It lacks details on output (no output schema) and doesn't differentiate from other retrieval tools, but suffices for a simple read operation.

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 already provides 100% coverage (pattern and required for 'subscription_id'). The description repeats 'by ID' without adding meaning, so it meets the baseline for well-documented parameters.

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 action ('Retrieve') and the resource ('a subscription by ID'). It immediately distinguishes itself from sibling tools like 'cancel_subscription' or 'list_subscriptions' by specifying retrieval by ID.

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 no guidance on when to use this tool over alternatives (e.g., 'list_subscriptions' to find IDs or 'retrieve_upcoming_invoice' for upcoming charges). There is no mention of context or prerequisites.

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