list_webhooks

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

No annotations are provided, so the description bears the full burden of disclosing behavior. It only states that the tool 'List all configured webhook integrations,' which is a read operation, but it does not mention permissions, rate limits, whether it returns only a list of IDs or full details, or any side effects. Given the lack of annotations, this is insufficient.

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 extremely concise, consisting of two short sentences. Every word serves a purpose: stating the function and providing a use case. No fluff or redundancy.

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 there are no parameters and no output schema, the description is minimally adequate. It tells the agent what the tool does and a use case, but it omits details about the structure of the response (e.g., fields returned, pagination). For a simple list tool, this might be acceptable, but richer context would improve it.

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 zero parameters, so there is no need for the description to explain parameters. The absence of parameters is implicit, and the description does not need to add value here.

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 all configured webhook integrations,' specifying a concrete verb and resource. It distinguishes itself from sibling tools by explicitly naming 'webhook integrations,' which is a distinct resource among many list_* tools.

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 provides context: 'Useful for auditing alert routing and notification channels.' This implies when the tool might be used, but it does not explicitly state when to use this tool versus alternatives or when not to use it. No comparison or exclusion criteria are given.

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