get_webhook_secret

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

With no annotations, the description carries the full burden and adds almost nothing: it does not state that this returns sensitive credential material, whether elevated permissions/API key scope are needed, whether the retrieval is audited, or that the value changes after a rotation. 'Current' hints at rotation linkage but is never explained.

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?

A single efficient sentence with the key qualifier ('current') front-loaded and no filler. It is appropriately sized, though there is no structure beyond the one line to organize the missing operational detail.

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?

No output schema, no annotations, and an undocumented parameter leave the agent guessing about the return shape (raw secret string vs. object with metadata), permissions, and failure modes. For a credential-exposing tool this is meaningfully under-specified.

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 0% — webhookId is documented only as a non-empty string. The description does not say whether the id is the webhook UUID, where to obtain it (list_webhooks/get_webhook), or what happens with an unknown or deleted webhook id.

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 gives a specific verb ('Retrieve') and a specific resource ('current HMAC signing secret for a webhook'), so the agent knows exactly what comes back. It does not differentiate itself from close siblings like get_webhook or rotate_webhook_secret, which is the only thing keeping it from a 5.

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?

There is no guidance on when to call this versus get_webhook (metadata) or rotate_webhook_secret (regenerate). No prerequisites, no exclusions, no mention of which lifecycle state (e.g., after create_webhook) the secret is valid in.

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