surveymonkey_list_webhooks

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

With no annotations, the description carries the full behavioral burden. It communicates an account-level read-only listing operation, which is useful, but it does not clarify whether pagination means the result may not actually include all webhooks in one call, nor does it disclose permission requirements or rate-limit behavior.

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 compact and front-loaded: one clear purpose sentence followed by a minimal parameter list. Every sentence earns its place and there is no redundant or filler content.

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?

For a simple two-parameter list operation with an output schema present, the description adequately covers scope and pagination parameters. It is slightly incomplete only in that it does not explicitly note pagination behavior or route users to get_webhook for individual lookups.

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 0% description coverage, so the description's Args section provides necessary meaning: 'page' is the page number and 'per_page' is results per page, with defaults. This adds value beyond the schema, though it omits potential details like valid ranges or maximum allowed values.

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 action and resource: 'Lists all webhooks in the account.' This is a specific verb-plus-resource statement that naturally distinguishes it from sibling webhook tools such as get_webhook, create_webhook, update_webhook, and delete_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 phrase 'all webhooks in the account' implies this is the enumeration tool, but the description does not explicitly say when to prefer it over get_webhook or provide any exclusions, prerequisites, or alternative routing. Usage context is only implied rather than stated.

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