sherweb_subscriptions_get

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

With no annotations, the description carries the behavioral burden. It discloses a non-obvious implementation detail: the tool reads a customer's subscription details and selects the matching subscription, which helps an agent understand the per-customer scoping. It does not mention error behavior or return format, but for a read operation this is still above average.

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 tight sentences with no filler. The primary purpose is front-loaded, and the second sentence earns its place by explaining the API constraint that is essential for correct invocation.

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 operation, the description is largely complete: it states what the tool does, the required pairing of IDs, and the non-obvious per-customer behavior. It could be slightly stronger by explicitly naming the list tool as the enumeration path, but nothing critical is missing for a correct call.

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 already fully documents both UUID parameters, so the baseline is 3. The description adds meaning beyond the schema by explaining why both IDs are required and how they relate: subscriptions are only exposed per customer, and the tool selects the match from that customer's subscription list.

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 ('Get') and resource ('one subscription's full details'), clearly signaling a singular lookup. The singular scope distinguishes it from sherweb_subscriptions_list, and the phrase 'full details' makes the intent unambiguous.

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?

It conveys an important usage constraint: Sherweb exposes subscriptions only per customer, so both customerId and subscriptionId are needed. However, it does not explicitly say when to use this tool instead of sherweb_subscriptions_list or that the list tool should be used first for enumeration.

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