get_subscription

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

No annotations are provided, so the description carries the full burden. It mentions that the tool returns the current status regardless of the subscription's status ('any status'), which adds useful behavioral context. However, it does not disclose potential error handling, pagination, or any side effects, though it is a simple GET operation.

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 two sentences with no waste. It leads with the core purpose and then adds a specific use case. Every word contributes to understanding the tool's function.

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 tool with a single parameter and no output schema, the description is sufficient to understand the basic purpose, but it lacks explicit parameter documentation and any mention of error behavior. The use case helps, but the absence of guidance on how to provide the subscription_id and what to expect as output leaves some gaps.

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 0% coverage for the subscription_id parameter, and the description does not mention this parameter at all. The agent only knows it is a required string, but the description does not clarify that it should be the subscription identifier, leaving interpretation to the tool name. Since the description should compensate for the schema gap, this is inadequate.

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 tool retrieves the current status of a single subscription, with the qualifier 'any status' to indicate it works across all subscription states. This differentiates it from sibling listing tools like list_subscriptions or get_customer_subscriptions, though it doesn't name them explicitly.

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 a concrete use case ('reconciling a lost webhook') which implies when to use it, but does not explicitly state when not to use it or contrast it with alternatives. The singular 'one subscription' implicitly suggests using it when you have a specific subscription_id, but the guidance is not fully developed.

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