list_webhooks

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

Discloses that signing secrets are redacted, which is a key behavioral trait. However, with no annotations, it doesn't mention pagination behavior (though cursor parameter implies it), response structure, or any side effects. Adds some value but insufficient for full transparency.

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?

A single sentence that front-loads the primary purpose and adds a critical detail (redacted secrets). Concise and efficient, but could be even more compact.

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?

Lacks output schema, so description should clarify return format (e.g., list of webhook objects). It only covers redaction. Adequate for a simple list operation, but incomplete for an agent to understand response structure.

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 coverage is 100%, so parameters are fully documented in the schema. The description adds no extra meaning beyond the schema descriptions. Baseline 3 is appropriate.

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 the tool lists webhook endpoints for the active sender, and adds a note about redacted secrets. It distinguishes from siblings like get_webhook (single) and create/update/delete, but could be more explicit about the resource type.

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?

No explicit guidance on when to use vs alternatives (e.g., get_webhook for a specific one). Usage is implied by the name and description, but no when-not or context provided.

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