Rotate PhishFort Webhook Secret

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

Annotations already indicate destructiveHint=true. The description adds that the secret is saved locally and not returned, which informs the agent about side effects (loss of secret in response). However, it does not disclose other behavioral traits like the need for approval or that the action is irreversible.

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 very short (one sentence) and front-loaded. However, given the complexity of the operation (7 params, destructive, requires approval), it is underspecified. The sentence is efficient but insufficiently structured for a tool with many parameters.

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 description lacks critical context: it does not explain the approval flow, the meaning of parameters, or what success looks like. The existence of an output schema is implied but not described. For a destructive tool with many required parameters, this is incomplete.

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 and 7 parameters (5 required), the description adds no meaning to the parameters. It does not explain what 'webhook_id', 'approval_id', 'approval_phrase', 'expires_at', 'request_digest', 'secret_output_name', or 'destructive_confirmed' represent. The agent must guess or consult external docs.

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 explicitly states 'Rotate webhook secret', clearly identifying the action (rotate) and resource (webhook secret). It distinguishes from create/update/delete webhook siblings by focusing on secret rotation. The addition 'One-time secret is saved locally, not returned' adds clarity, though it could elaborate on the rotation process.

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 no guidance on when to use this tool versus alternatives like update_webhook. There is no mention of prerequisites, context, or scenarios where rotation is appropriate. The agent must infer usage from the name alone.

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