list_webhooks

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It merely states 'List webhooks' without mentioning read-only nature, pagination, ordering, scope (e.g., all webhooks or filtered), or return format. This is a minimal behavioral disclosure, though the action itself implies a read operation.

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 phrase that does not waste words. It is appropriately short for a simple list operation, though it could have included a touch more context without becoming verbose. The clean structure earns a high score.

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 simplicity (no parameters, no annotations, no output schema), the description is minimally adequate but not fully complete. It fails to mention what the returned data looks like or any characteristics of the webhook list (e.g., ordering, structure). Since there is no output schema, the description should at least indicate the result type, making completeness slightly 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?

The tool has zero parameters, so the schema provides complete coverage (100%). The description correctly avoids redundant parameter information. Baseline of 4 applies because there is nothing to document; no additional semantic value is needed.

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 states a clear verb ('List') and resource ('webhooks'), making the purpose obvious. It distinguishes from create/delete webhook siblings by the action, but does not explicitly differentiate or add scope details. Adequately clear for a simple list operation.

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?

No guidance is provided on when to use this tool versus alternatives. The context implies it is for retrieving webhooks, but there is no explicit mention of when to choose it over similar list tools or the create/delete operations. The description leaves usage entirely to inference.

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