list_webhook_subscriptions

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's contribution is minimal. It adds that the tool returns a list, but no further behavioral details (e.g., pagination, ordering). No contradiction with annotations.

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, using a clean Args/Returns structure. Every sentence adds value, with no redundancy or filler.

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?

Given the simple tool (2 optional parameters, output schema exists), the description covers the essentials. It lacks explicit mention of default behavior when no filter is provided (likely lists all), but this is implied. The return format is not detailed, but the output schema handles that.

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%, but the description provides meaningful parameter details: 'filter_type' options are enumerated ('account_reference', 'service_reference', 'team_reference') and 'limit' is explained as 'Max results to return'. This adds significant context beyond the schema types.

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 states 'List webhook subscriptions' which clearly indicates the action and resource. It is specific enough to distinguish from sibling tools like 'list_services' or 'list_teams', but does not explicitly differentiate from 'get_webhook_subscription' (a single-resource fetch vs list).

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'get_webhook_subscription' for a single subscription). The description does not mention scope, prerequisites, or exclusions.

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