rotate_webhook_secret

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

With no annotations, the description carries the behavioral burden. It discloses two critical traits: the new secret is returned exactly oncechers, and the old secret stops verifying immediately. This conveys the irreversible, high-impact nature of the operation well, though it could also mention permissions or an explicit 'cannot be undone' warning.

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 two sentences with no filler. The action is front-loaded, the endpoint is included for precision, and the second sentence adds the most operationally important caveat.

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 single-parameter tool with no output schema, the description is complete: it says what happens, what the caller receives, and the immediate consequence. The critical one-time-only availability of the secret is explicitly stated, which is exactly what an agent needs to know.

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 coverage is 100% and the only parameter, id, is already described as 'The webhook id.' The description adds no extra meaning to the parameter beyond what the schema provides, so the baseline of 3 is appropriate.

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 specific verb ('Rotate') and resource ('webhook signing secret') and even gives the exact endpoint. This clearly distinguishes it from sibling tools like update_webhook, verify_webhook_signature, and test_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 context is clear: this tool is for rotating a webhook signing secretholistically, and the behavioral consequences of rotation are stated. It doesn't explicitly name alternatives or exclusion conditions, but the unique action and endpoint make the intended use obvious.

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