zuckerbot_rotate_webhook_secret

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

Without annotations, the description fully discloses critical behavior: the new secret is returned exactly once in this response, and every other read shows only metadata. The old secret stops authenticating immediately. This goes beyond basic purpose to explain side effects and one-time nature.

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 front-loaded with the action. Every sentence adds essential information: purpose, one-time return behavior, and immediate invalidation. No redundancy or filler.

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?

Given no output schema, the description adequately explains the return value (new secret in response, only once) and the condition (old secret stops working). For a single-parameter tool, this is fully complete.

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?

The input schema has 100% description coverage for the sole parameter (`business_id`), and the tool description does not add any additional meaning to what the schema already provides. The baseline score 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 uses the specific verb 'Rotate' and resource 'Conversions API webhook secret for a business', clearly identifying the tool's function. It is distinct from sibling tools which cover other operations like deleting audiences, getting insights, or syncing conversions, making it easy for the agent to select correctly.

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 clearly states the immediate effect (old secret stops authenticating) and the necessary follow-up action (update the system that signs inbound webhooks). It implies the tool should be used when ready to update, but does not explicitly list when not to use it or provide alternative tools.

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