list-webhooks

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

Despite no annotations, the description implies a read-only list operation. However, it lacks details on pagination, ordering, or rate limits, which are typical for list endpoints.

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 sentence with no extraneous information. Key information is front-loaded and every part serves a purpose.

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 list tool with one parameter and no output schema, the description covers purpose and parameter. However, it omits common list behaviors like pagination or default response fields, leaving potential 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?

Schema coverage is 100% for productId. The description adds value by explaining its role and pointing to the source endpoint for obtaining it, beyond the schema's type/format.

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 it returns a list of webhooks for a given product, using specific verb and resource. It distinguishes from sibling tools like get-webhook (single), create-webhook, delete-webhook, etc.

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 explains that productId is required and can be obtained from the list-products endpoint, providing clear context. However, it does not explicitly state when not to use this tool or mention alternative filtering options.

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