List webhook endpoints

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

No annotations are provided, and the description does not disclose any behavioral aspects such as whether it performs a read-only operation, potential rate limits, or how the list is ordered. It is a simple statement without additional context, leaving the agent without safety or performance expectations.

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 concise and clear, but it lacks structure. It is a single sentence that does not front-load any critical details beyond the resource. It is not verbose, but also not particularly well-structured for quick scanning.

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 simplicity and no output schema, the description could mention the purpose of listing endpoints (e.g., to inspect configuration, troubleshoot delivery) and perhaps note that no filtering is possible. It is incomplete for an agent that needs to understand the value of this tool in context.

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 takes 0 parameters)Skip, so the description need not explain parameter details. The schema coverage is 100% (vacuously), and the description adds a bit of context about the resource type. Scores high because there is no semantic burden on the description.

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 purpose: listing webhook endpoints of the platform, but it is somewhat generic and could be more specific about what distinguishes it from other list tools. It does not explicitly mention filtering or pagination, but the resource is clearly identified as 'webhook endpoints'.

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?

There is no guidance on when to use this tool versus alternatives. The sibling tools include other list resources, and the description doesn't mention any context or exclusions. An agent is left without any direction on when this is the appropriate choice.

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