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

No annotations are provided, so the description carries the burden. 'List all your webhooks' transparently implies a read operation with no side effects, which is adequate for a simple listing tool. It does not disclose pagination behavior or sorting, but these are already covered by the input schema and output schema, so no serious gap exists.

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 compact: a one-sentence purpose statement followed by a concise 'Use when' bullet list. Every sentence earns its place, and the most important information is 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?

For a simple list operation with no required parameters, a fully detailed schema, and an output schema, the description is nearly complete. It explains what the tool does and when to use it. It could be more complete by explicitly contrasting with resource-scoped webhook tools, but this is not a significant gap.

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 100%, so all four parameters (page, api_key, page_size, project_id) are already documented in the schema. The description adds no additional parameter-level semantics beyond stating the use case for finding webhook_id.

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 specific verb and resource: 'List all your webhooks', and clarifies scope with 'configured in your account'. This clearly distinguishes it from single-webhook retrieval (get_webhook) and resource-scoped listing (list_resource_webhooks) by emphasizing the account-wide scope.

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 'Use when' section explicitly gives two concrete scenarios: viewing all webhook endpoints and finding a webhook_id for monitors/jobs. It provides clear context for when to call this tool, though it does not explicitly state when not to use it or name alternative tools.

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