webhooks_list

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

The description discloses the tool is 'Read-only,' which matches the annotations readOnlyHint: true, destructiveHint: false, and idempotentHint: true. It also lists the fields returned, providing additional behavioral context. No contradictions with annotations.

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 very concise with two sentences, no redundant words, and essential information front-loaded. Every sentence adds value.

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?

Considering there is only one parameter, no output schema, and annotations already cover safety, the description covers the essential aspects: what it does, what it returns, and how to use the results. The missing explanation of the 'site' parameter prevents a perfect score.

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 one required parameter 'site' with no description, and schema description coverage is 0%. The description does not explain what 'site' represents or how to specify it (e.g., site ID or name). This is a significant gap for a required parameter.

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 webhooks on the site' and enumerates the fields returned (id, enabled, target, event, url, target_id, description). It uses a specific verb 'List' and specifies the resource 'webhooks on the site,' distinguishing it from sibling tools like webhook_create, webhook_delete, and webhook_update.

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 instructs to 'Use the returned id for webhook_update / webhook_delete,' providing clear guidance on how to use the output. It also explicitly states 'Read-only,' setting expectations. However, it does not explicitly state when not to use the tool or mention alternative tools for other operations.

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