list-webhooks

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

With no annotations, the description must disclose behavioral traits. It only states the basic list function and optional filter, omitting details like read-only nature, pagination behavior, or any limitations. This is insufficient for an agent to fully understand side effects or constraints.

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, efficient sentence with no wasted words. However, it could be slightly expanded to include minimal behavioral context without losing conciseness.

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 the simplicity of the tool and full schema coverage, the description is largely adequate. It lacks explicit mention of return format (list of webhook objects) or default behavior, but the agent can infer most needed details from the tool name and parameters.

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 100% coverage, and the description adds no extra meaning beyond the schema. The mention of 'optionally filtered by model name' corresponds to the existing modelName property, but does not enhance understanding of maxResults or pageToken.

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 verb 'List' and the resource 'webhooks', with an optional filter by model name. This effectively differentiates the tool from its siblings like create-webhook, delete-webhook, get-webhook, and update-webhook.

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 implies use for listing webhooks, but provides no explicit guidance on when to use this tool over alternatives (e.g., get-webhook for a single webhook) or when not to use it. Usage context is minimally implied.

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