sherweb_subscriptions_list

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

With no annotations, the description bears the full burden of behavioral disclosure. It usefully states the returned attributes, which clarifies the output content, but it does not mention pagination, limits, ordering, authorization requirements, or error behavior.

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 that states the action, scope, and returned fields with no filler. Every phrase contributes useful information.

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 one-parameter list operation with no output schema, the description is largely complete: it states what is listed and which fields are returned. The main gap is lack of pagination or result-limit information, but this does not prevent correct invocation.

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 fully documents the single parameter (customerId as a UUID), so schema coverage is 100%. The description adds only the implicit context that subscriptions belong to a customer, which aligns with the parameter but does not meaningfully extend its semantic meaning.

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 uses a specific verb ('List') and resource ('a customer's subscriptions'), and enumerates the returned fields: product name, SKU, quantity, billing cycle, purchase date, fees, and commitment term. It is clear in intent, though it does not explicitly differentiate from sibling sherweb_subscriptions_get by naming it.

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 the tool is used when you need all subscriptions for a specific customer, with the customerId required. However, it provides no explicit guidance about when not to use it or when to prefer siblings such as sherweb_subscriptions_get.

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