surveymonkey_delete_webhook

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the action is deletion, but does not mention that deletion is permanent, whether it has any side effects, or what permissions are required. For a destructive operation, this is a significant gap.

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 short, front-loaded with the core action, and easy to scan. The Args section is simple and appropriately sized for a one-parameter tool. It loses one point because the parameter line is largely redundant with the schema title.

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 one-parameter delete operation with an output schema, the minimum invocation information is present: the webhook_id. However, without annotations or guidance about preconditions, irreversibility, or error behavior, the definition is only minimally adequate. The output schema covers return values, so that absence is not penalized.

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%, so the description needed to add semantic meaning to the parameter. 'webhook_id: Webhook ID' merely repeats the schema property title, adding no information about format, source, or constraints. This provides minimal value beyond the structured schema.

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 states a clear, specific action and resource: 'Deletes a webhook.' Among the sibling CRUD tools, it is unambiguous that this tool is for removing an existing webhook rather than creating, reading, or updating one. The Args line reinforces the target by webhook_id.

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?

No guidance is provided about when to choose this tool over alternatives such as update_webhook or get_webhook. The only usage signal is the verb 'Deletes,' which must be inferred rather than explicitly stated. There are no prerequisites, exclusions, or alternative routing details.

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