Delete PhishFort Webhook

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

The description adds the behavioral note 'after approval', which is not in the annotations. However, with destructiveHint=true already declared, the description could further detail the destruction's reversibility, side effects, or the confirmation mechanism (destructive_confirmed parameter).

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 only eight words, which is under-specified rather than concise. It lacks essential information about parameters, usage, and output, making it ineffective despite its 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?

The tool has six parameters, an output schema, and a multi-step flow implied by 'after approval'. The description fails to explain any of these, leaving the agent without guidance on how to call the tool correctly.

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?

With 0% schema description coverage, the description must explain the six parameters. It does not mention any parameter, including critical ones like webhook_id, approval_id, approval_phrase, expires_at, request_digest, or destructive_confirmed. This is a severe 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 the action 'delete' and the resource 'webhook subscription', with the qualifier 'after approval'. This is specific enough to distinguish from read operations, but it could be more explicit about what type of webhook or the approval context.

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 on when to use this tool versus alternatives like phishfort_update_webhook or phishfort_test_webhook. The phrase 'after approval' hints at a precondition but does not specify scenarios, prerequisites, or when not to use it.

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