list_webhooks

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

With no annotations, the description carries the full burden of behavioral disclosure. It merely states the action without revealing pagination behavior, return structure, or any side effects. It does not mention that results may be filtered via the 'q' parameter or limited by 'per_page'. This is a minimal disclosure.

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 extremely concise at two words, with no filler or redundant information. Every word earns its place, and the structure is direct and front-loaded.

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?

Given the tool's low complexity and a thorough input schema, the description is minimally viable. However, it lacks any mention of pagination, filtering, or return payload, relying entirely on the schema for context. For a list operation with no annotations or output schema, richer context would be helpful, but the description is not inadequate.

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 input schema covers 100% of the parameters with descriptions, so the baseline is 3. The description adds no additional semantic meaning beyond what the schema already provides. However, it does not contradict the schema, and the schema is self-explanatory.

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 'List webhooks' uses a specific verb and resource, clearly stating the tool's action. It distinguishes from sibling tools like 'get_webhook' (singular) and 'create_webhook' by indicating a list operation for multiple webhooks.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that filtering or pagination are available, nor does it contrast with 'get_webhook' for fetching a single webhook. No usage context is provided.

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