list_webhooks

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

No annotations are provided, so the description carries the full burden. The description indicates a read-only operation ('list'), which is consistent with the lack of destructive hints. However, it doesn't disclose any additional behavioral traits such as pagination, rate limits, or authentication requirements.

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 five words, perfectly concise. It front-loads the action and resource with scope, and every word earns its place.

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 that the tool has zero parameters and no nested objects, the description is complete enough for its simplicity. The output schema exists, so return values don't need elaboration. A minor gap is the lack of mention of pagination or limits, but for a simple list all tool, this is acceptable.

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 has no parameters, so the description doesn't need to add parameter semantics. The schema coverage is 100% (vacuously true), and the description correctly implies no filters are needed since it lists all user-level webhooks. This is a 4 because the description adds clarity in the absence of parameters.

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 all user-level webhooks' clearly states the action (list) and the resource (webhooks), specifying the scope (user-level). This distinguishes it from siblings like list_team_event_type_webhooks and list_event_type_webhooks, which operate on different scopes.

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 implies use when you need to list webhooks at the user level, but it doesn't explicitly state when to use this vs. alternatives like list_event_type_webhooks or list_team_event_type_webhooks. The context from sibling names helps, but the description lacks explicit guidance.

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