get_webhook_secret

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

Since no annotations are provided, the description carries the burden of behavioral disclosure. It conveys a read-only action ('Retrieve') but does not explicitly state the absence of side effects, sensitivity of the secret, or any authentication requirements. This is adequate for a simple getter but leaves room for more transparency.

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 a single sentence with no filler. It front-loads the key information (what is retrieved) and adds the purpose efficiently. Every word earns its place.

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 tool with no parameters and no output schema, the description sufficiently explains what the tool does and why it would be used. An agent can confidently call it when needing the webhook signing secret for callback verification without missing essential context.

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 tool has zero parameters, so the description does not need to explain parameters. The baseline for 0 params is 4, and the description adds useful context about the secret's purpose without needing to elaborate on inputs.

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 'Retrieve' and identifies the resource as the 'merchant webhook HMAC signing secret'. It also explains the purpose ('used for verifying webhook callbacks'), which distinguishes it from sibling tools like 'get_webhook_deliveries' that retrieve delivery records rather than secrets.

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 gives context by stating the secret is used for verifying webhook callbacks, implying when this tool would be needed. However, it does not explicitly compare to alternatives or state when not to use it, such as when rotating the secret via 'regenerate_api_keys'. The usage guidance is implied rather than explicit.

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