List Webhooks Resources API Versions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the tool's safety is clear. The description adds pagination behavior ('Returns a paginated JSON array... Use page and per_page to control pagination; the response includes pagination metadata'), which goes beyond annotations. No contradictions.

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 three sentences covering purpose, usage, and pagination. It includes an API reference line that may be redundant for an AI agent. Still, it is clear and front-loaded.

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?

The tool has no output schema, so the description must explain the return value. It mentions a 'paginated JSON array of Webhooks' and pagination metadata, but does not detail the fields within each webhook resource API version object. For a list tool, this is adequate but could provide more 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?

The input schema covers all 3 parameters with descriptions (100% coverage). The description adds meaning by explaining how page and per_page work together for pagination and that the response includes pagination metadata, which is not in the schema descriptions.

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 returns a list of Webhook Resources API Versions and enumerates specific use cases like paginated overview, finding IDs, and filtering. It uses a specific verb (return) and resource, and is distinct from sibling 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 explicit usage context: 'Use this to enumerate Webhooks when you need a paginated overview, to find IDs, or to filter by query parameters.' It also mentions required parameter project_id and pagination controls. However, it does not explicitly distinguish when to use this tool versus other webhook-related tools (e.g., list_webhooks_hooks).

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