Get subscription

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is well established. The description adds useful context about the returned contents, but does not disclose behavior for missing subscriptions or error conditions. No contradiction with annotations.

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 concise sentence, front-loaded with the action and resource, and includes the most relevant detail about the returned data. There is no filler, repetition, or unnecessary background.

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 read-only retrieval with rich annotations and a documented optional administration_id, the description covers what is retrieved and the key return contents. It lacks an explicit pointer to list_subscriptions or error behavior, but these are minor given the tool's low complexity.

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 only 50%, so the description was expected to add parameter meaning, but it only describes the output contents, not the parameters. subscription_id is self-explanatory and administration_id is already documented in the schema, leaving the description with no added parameter-level value.

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 specific verb ('Retrieve'), a precise resource ('one subscription'), and the key contents (product, billing cycle, recurring invoice). The singular 'one' clearly differentiates it from list_subscriptions among the siblings.

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 phrase 'one subscription' implies this is for fetching a single record versus listing, but the description does not explicitly mention when to prefer this tool over list_subscriptions or any other alternative. Usage context is left to inference rather than being stated directly.

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