Rotate Webhook Secret

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

The description provides key behavioral details beyond annotations: old secret is immediately invalidated and new secret is only shown once. This adds critical context for the agent about side effects and return value handling.

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?

Two concise sentences, no wasted words, front-loaded with the action. Efficient.

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?

Covers essential behavioral aspects for a simple mutation tool. Minor gap: no parameter explanations. But output schema exists (though not shown) and description hints at return. Adequate for the complexity.

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 should explain parameters but does not. Parameters (webhook_id, org_uuid, request_id) are not mentioned, leaving the agent to infer their meaning from context.

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 uses a specific verb+resource ('Rotate the signing secret for an Automox webhook') and clearly distinguishes from sibling tools like create_webhook, update_webhook, and delete_webhook. It states the exact action and what changes.

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 explicit when-to-use vs alternatives is given, but the purpose is clear enough that an agent can infer when to call this tool. It does not mention when not to use it or compare to other webhook-related tools.

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