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

Annotations already state readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered by structured fields. The description adds nothing beyond the path and the describe_operation pointer (no pagination, filtering, or response shape), so it does not earn credit for behavior.

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?

It is short but wasteful: the first sentence is duplicated verbatim, and the remaining content is an operation ID and a redirect note rather than front-loaded meaning. No sentence 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?

No output schema exists and the parameter schema is essentially free-form with no documented keys, so the description should explain what filtering is possible and roughly what the endpoint returns. It only points at describe_operation, leaving the agent to make a second call to understand even the basics.

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?

There are 2 parameters (query and params) with 0% schema description coverage, and the description mentions neither, not even to say that query accepts arbitrary filter keys. It fails to compensate for the complete documentation gap.

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 repeats the raw endpoint string 'GET /api/webhooks/incoming' twice, which merely restates the tool name and title. It gives no verb-level explanation of what an agent gets back (a list of incoming webhook configurations?) or how it differs from the sibling 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?

The only guidance is the pointer that 'describe_operation provides native request schemas,' which is a hint about schema discovery rather than when to call this tool versus describe_operation, execute_read, or the outgoing-webhooks sibling. No when/when-not conditions or prerequisites are stated.

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