rotate_webhook_secret

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

Discloses critical behavior: single retrieval, 24h overlap, authentication requirement. With no annotations, it covers essential safety and mutation aspects well, though could elaborate on effect of repeated calls.

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 sentences, no wasted words. Front-loaded with action, then key constraints. Every sentence provides unique value.

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?

Adequately covers behavior and prerequisites for a zero-parameter tool with no output schema. Minor gap: does not describe output format or type of the returned secret.

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?

No parameters exist, baseline is 4. Description adds context about the operation (single return, grace period) that complements the empty 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 clearly states the action ('Generate a fresh HMAC signing secret') and the specific resource ('operator's webhook endpoint'). It differentiates from sibling webhook tools by specifying 'operator's' rather than mailbox webhooks.

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?

Provides key usage constraints: secret returned exactly once, previous valid for 24h, requires operator_passkey. Implicitly guides when to use (for rotation) but does not explicitly contrast with alternatives.

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