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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, this endpoint exposes a credential (a webhook signing secret), and the description says nothing about sensitivity, permission requirements, or rotation/caching implications — context that matters far more here than for an ordinary read.

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 single meaningful sentence is duplicated verbatim, so the description is simultaneously redundant and under-specified. The operation-ID sentence is boilerplate that conveys nothing about 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?

With no output schema and no annotations covering return content, the description should at minimum state that the response contains the secret value and its format. For a security-sensitive retrieval endpoint with 0% parameter documentation, the definition leaves too much for the agent to infer.

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% with two parameters (query and params.id), and the description adds no meaning to either. It never clarifies that 'id' is the outgoing webhook identifier, nor what the free-form 'query' object is for, so an agent must guess from the schema structure alone.

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 only repeats the endpoint path 'GET /api/webhooks/outgoing/:id/secret' twice, which restates the title and name rather than explaining in plain language that it fetches the signing secret for a specific outgoing webhook. An agent can infer the resource from the path, but there is no verb-plus-resource statement of intent and no differentiation from siblings like get_webhooks_outgoing_ec27882af290f545aaaabd1e.

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 indication of when to call this tool versus the sibling outgoing-webhook endpoints or the deliveries endpoint. The only forward-looking sentence points to describe_operation for native request schemas, which is a schema-discovery hint, not usage guidance or an exclusion rule.

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