subscriptions.retrieve

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says "Retrieve" which implies a read operation, but it does not explicitly confirm read-only behavior, describe the response format, or mention error conditions (e.g., not found). The description lacks transparency about side effects and return value.

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, focused sentence with no unnecessary words or filler. It is front-loaded with the action and target, making it extremely concise and scannable.

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 param, no output schema), the description is adequate but not thorough. It omits any mention of what the response contains (e.g., full subscription object), error handling, or specific use-case context, which would be useful for an agent to fully understand the tool's behavior.

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 covers the sole parameter 'id' with a description of 'Subscription ID', giving 100% coverage. The description does not add any additional meaning beyond the schema, which is the baseline expectation for high schema coverage.

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 "Retrieve a subscription by ID" uses a specific verb and resource, clearly distinguishing it from siblings like subscriptions.list (which lists multiple) and subscriptions.create/update/cancel (which mutate). It precisely communicates the tool's function and scope.

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 implies usage when you have a specific subscription ID and need its details, but it does not explicitly state when to prefer this over subscriptions.list or other alternatives. No exclusions or alternative tool mentions are provided, so guidance is only implicit.

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