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

With no annotations, the description's burden is higher. It discloses the tool provides status and failure reasons, which is helpful. However, it doesn't disclose any side effects (likely none since it's a list), nor does it mention pagination, ordering, or whether the output includes all webhooks for the owner. It's a read-only list, but this isn't explicitly stated.

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 extremely concise, a single sentence that communicates the key value proposition. It is front-loaded with the resource ('URLs') and immediately conveys the tool's purpose without any fluff.

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 list tool with one parameter and no output schema, the description should cover what output looks like and any filtering or behavior. It misses pagination, return format, and any assumptions about the 'owner' parameter. The description is too minimal to fully guide an agent, especially with zero schema coverage.

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% and the description does not explain the 'owner' parameter beyond what the schema shows (it is a string). The description implies it lists webhooks for a specific owner but does not clarify the format, required format, or what 'owner' refers to. The description fails to compensate for the lack of schema documentation.

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 it lists registered webhook URLs, their status, and why the hub stopped calling. It uses a specific verb and resource, though it does not explicitly mention the owner parameter or differentiate from set_webhook, but the focus on listing and status makes the purpose clear.

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 implies it should be used to retrieve webhook information but provides no guidance on when to use this over alternatives like set_webhook or forget_webhook. No explicit context or exclusions are given.

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