rotate_webhook_secret

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

With no annotations, the description fully covers behavioral traits: the secret is returned exactly once, previous secret remains valid for 24h, and it requires operator_passkey assurance. These details disclose critical mutation behavior without contradiction.

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 three sentences, each adding essential information: action, uniqueness of return, grace period, and authentication requirement. No wasted words.

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 covers the key aspects of the tool. However, without an output schema, it could mention the format or structure of the returned secret to fully inform the agent. Otherwise, it is sufficient for a simple generation tool.

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 in the schema, and schema coverage is 100%. The description adds no parameter info, but none is needed. The baseline is met.

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 tool generates a fresh HMAC signing secret for the operator's webhook endpoint. It specifies the secret is returned exactly once and that the previous secret remains valid for 24 hours. This differentiates it from sibling tools like set_secret or delete_secret.

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 implies use when rotating the webhook secret and mentions the 24-hour grace period. However, it does not explicitly exclude alternatives or provide guidance on when not to use this tool compared to other secret management tools.

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