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

The description adds substantial behavior beyond the annotations: the previous secret is invalidated immediately, the replacement is returned only once, it must be stored and applied by the receiver, inactive or unknown subscriptions return not_found, and there are no automatic retries. These details go well beyond the destructive and non-idempotent hints.

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 four efficient sentences, front-loaded with the action and immediate invalidation effect. Each following sentence adds distinct, useful information about permissions, one-time return handling, error behavior, and retry behavior.

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 destructive, non-idempotent mutation with one parameter and no output schema, the description covers the critical missing context: required permission, immediate invalidation, one-time secret return, storage guidance, error behavior, and lack of automatic retries. An agent has enough information to invoke it correctly and warn the caller about handling 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?

Schema description coverage is 0%, so the schema only supplies the UUID format and pattern for webhookId. The description adds meaning by indicating that the identifier must refer to an active webhook subscription and that inactive or unknown subscriptions return not_found, but it does not explain where to obtain the webhookId or otherwise fully compensate for the missing parameter description.

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 and resource: rotating an active project webhook signing secret, with the immediate invalidation scope. This clearly distinguishes the operation from sibling create/delete webhook tools without needing to inspect schemas.

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?

It specifies that rotation applies to an active webhook subscription and notes the required webhooks.write permission, which gives clear usage context. It does not explicitly name alternatives such as using create or delete webhook, but the operation is specialized enough that this is a minor gap.

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