list_webhooks

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

With no annotations, the description carries the full burden. It discloses the returned fields (topic, delivery format, endpoint, etc.) and mentions filtering by topic. However, it does not explain pagination behavior (though schema suggests it via 'first' and 'after' parameters) or potential performance implications of listing many webhooks.

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 concise, with no unnecessary words. It front-loads the core action and then adds relevant details in a structured manner, making it easy for an AI agent to parse quickly.

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?

Despite lacking an output schema, the description lists key return fields (topic, delivery format, endpoint, API version, filters). It also explains the filtering option. It does not mention pagination or ordering, but overall it provides sufficient context for a list operation.

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?

Only 33% of parameters have schema descriptions. The description adds value by explaining the 'topics' filter and providing example values. It does not elaborate on 'first' (page size) or 'after' (cursor) beyond their schema definitions, which is a gap given low 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 clearly states the tool's purpose: 'List webhook subscriptions on the store.' It explains what webhooks are and mentions specific event topics, delivery targets, and returned fields. This distinguishes it from siblings like 'create_webhook', 'delete_webhook', and 'get_webhook'.

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 advises using the tool to 'audit existing automation hooks before creating new ones,' which provides clear context for when to use it. However, it does not explicitly state when not to use it or mention alternatives like 'get_webhook' for individual subscriptions.

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