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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds nothing beyond structured data: no return shape, no pagination behavior, no filtering semantics for the query parameter — just a duplicated route and an operation ID.

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 route string is repeated verbatim in consecutive sentences, which is pure waste. The one genuinely informative clause (describe_operation pointer) is buried at the end after the duplication.

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, 0% parameter coverage, and a nested free-form query object, the description should carry substantial weight. It instead supplies only an operation ID and a redirect to describe_operation, leaving an agent unable to infer what the endpoint returns or how to filter.

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% and the two parameters (query, params) are opaque, with nested objects allowed in 'query'. The description compensates only by redirecting to describe_operation; it gives no meaning, format, or examples for what belongs in query.

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 restates the HTTP route (twice) — 'GET /api/webhooks/outgoing' — which is effectively a tautology of the name and title. It never says in plain language that it lists outgoing webhook subscriptions, nor does it distinguish itself from siblings like get_webhooks_outgoing_by_id_secret or get_webhooks_incoming.

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 a single useful pointer — 'describe_operation provides native request schemas' — which tells the agent where to get parameter detail, but there is no guidance on when to use this tool versus the outgoing-webhook-by-id or incoming-webhook siblings.

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