list_webhooks

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

With no annotations provided, the description carries the full burden. It only states the basic function without disclosing pagination (after, first parameters), default behavior, ordering, or required permissions. A user would not know that results are paginated or that workspace parameter may be required.

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 concise sentence, which is efficient but sacrifices necessary detail. It is front-loaded with the core action, but omits crucial context about parameters and behavior.

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 has three optional parameters (including pagination) and an output schema, the description is incomplete. It does not explain that the result is paginated, how to use 'after' for cursor-based pagination, or that 'workspace' might be required. The output schema exists, so return structure is covered, but usage context is lacking.

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 description coverage is 0%, and the description adds no information about the 'after', 'first', or 'workspace' parameters. The agent cannot infer their meanings or constraints from the description alone.

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 'List webhooks configured for the workspace,' which identifies the action and resource. It distinguishes from sibling tools like get_webhook (single) and create/update/delete, but does not mention pagination or scope limitations.

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?

Usage is implied: use when a list of webhooks is needed. No explicit guidance on when to use this vs alternatives like get_webhook for single webhooks, nor any conditions or prerequisites.

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