listWebhookConfigurations

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

With no annotations provided, the description carries the full behavioral burden. It adds the valuable disclosure that secrets are redacted, and 'List' implies a read-only, non-destructive operation. It does not mention pagination or auth requirements for owner_email, but for a simple listing these are not critical gaps.

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 no filler, front-loading the action and resource, and the note about secret redaction earns its place by adding meaningful behavioral context.

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?

There is no output schema, so the description does not clarify the return shape beyond the implied 'list', and pagination is unmentioned. However, the tool is low-complexity, parameters are fully schema-documented, and the description covers the core behavior; it is minimally adequate with some inference required.

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%, with agent_id and owner_email already documented in the schema. The description adds no parameter-specific details beyond referring to 'an agent', so it provides no additional value over the structured schema.

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 the specific operation ('List') and resource ('webhook configurations'), scoped to an agent and event types (on_call_start / on_call_end). It distinguishes this read operation from the sibling upsertWebhookConfiguration without needing to open the schema.

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 makes clear what the tool does and for whom, but it does not explicitly say when to prefer this over the sibling upsertWebhookConfiguration, nor does it state any exclusions. The contrast between 'list' and 'upsert' is implied rather than stated.

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