list_webhook_subscriptions

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

With no annotations, the description carries the full burden. It discloses a crucial behavioral trait: only shop-scoped subscriptions are returned, not app-scoped subscriptions. This adds meaningful context beyond the schema, though it omits other behaviors like read-only status or pagination, which are partially implied by the name and schema.

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 that front-loads the primary action and immediately adds a critical scope caveat. Every word serves a purpose, with no redundant 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 straightforward list operation with optional filters and no output schema, the description provides the essential scope distinction and is sufficiently complete for an agent to select and invoke the tool. It doesn't describe return fields, but that is not necessary given the simple nature and well-covered schema.

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 descriptions cover 100% of parameters, so the baseline of 3 applies. The description adds no extra parameter details beyond stating 'list all', but the schema's parameter descriptions are self-explanatory, making this sufficient.

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 lists all webhook subscriptions for the current app and shop, using a specific verb ('List') and resource ('webhook subscriptions'). It distinguishes from siblings like get_webhook_subscription (singular) by emphasizing the collection scope and the shop-scoped filter.

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 clear context that this tool returns shop-scoped subscriptions and explicitly excludes app-scoped ones, preventing misuse. However, it does not explicitly name alternative tools for retrieving a single subscription, so it misses the top score for explicit when-to-use guidance.

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