List Webhooks

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is clear. The description adds behavioral context by stating 'Supports cursor-based pagination,' which is beyond annotations. However, it does not disclose other potential traits like authentication needs or rate limits, but given the annotations, the bar is lower.

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 two sentences, making it concise and front-loaded with the purpose. However, it lacks parameter information that could be included without significant bloat. Each sentence serves a purpose (purpose and pagination), but the overall conciseness sacrifices completeness for brevity.

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 tool has 4 parameters with 0% schema coverage and an output schema exists, the description should compensate by explaining the parameters. It does not, so an AI agent may struggle to invoke it correctly. The presence of many sibling tools adds to the need for clearer differentiation, which is absent here.

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 description coverage is 0%, meaning no parameter descriptions in the input schema. The description only mentions cursor-based pagination but does not explain the purpose of org_uuid, limit, cursor, or output_format. Without any parameter semantics, an AI agent may not know how to use these parameters correctly, leaving a significant gap.

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 webhook subscriptions for the Automox organization', providing a specific verb (list) and resource (webhook subscriptions). This distinguishes it from siblings like create_webhook, delete_webhook, get_webhook, and other webhook-related list tools such as list_webhook_deliveries and list_webhook_event_types.

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 does not provide explicit guidance on when to use this tool versus alternatives. It lacks when-not-to-use conditions and does not mention any prerequisites or comparisons with other list tools or webhook-specific tools. The only additional information is about pagination, but no context on selecting this over get_webhook or other filtered lists.

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