list_webhook_subscriptions

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

With no annotations, the description carries the burden of disclosing behavior. It does reveal the 'active' filter, which is a meaningful behavioral trait. However, it does not explicitly state that the operation is read-only, nor does it mention pagination, rate limits, or authentication context. For a list tool, this is minimal but not misleading.

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 unnecessary words, making it efficient and front-loaded. However, it is under-specified due to the omission of parameter semantics, which prevents a perfect score.

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 one optional parameter and an output schema, the description covers the core action but omits the meaning of max_items and any behavioral constraints like pagination or default limits. With no annotations, this leaves significant gaps in the agent's understanding. The output schema does not compensate for missing parameter guidance.

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 schema defines max_items with a default but no description (0% coverage). The description does not mention this parameter at all, so an agent would not understand what max_items controls or how it affects results. The description fails to compensate for the schema's lack of parameter explanation.

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 uses the specific verb 'List' with a clear resource 'webhook subscriptions', scoped to 'active' and 'on the account'. This clearly distinguishes it from sibling tools like create/delete_webhook_subscription and other list tools.

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 states what the tool does but provides no explicit guidance on when to use it vs alternatives. Usage is implied by the name and verb, but there is no reference to when not to use it or which alternative to prefer.

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