list_webhook_subscriptions

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

No annotations are provided, so the description must fully disclose behavior. It only states the basic purpose without mentioning pagination, rate limits, authentication needs, or what constitutes 'active'. This is insufficient for a safe agentic selection.

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 4 words, front-loading the verb and resource. No unnecessary content; every word 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?

Given there is an output schema (unseen), the description is mostly complete for a simple list tool. However, it could elaborate on what 'active' means and whether any implicit filters apply, but is sufficient given the tool's simplicity.

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 tool has zero parameters, and schema coverage is 100%. Per guidelines, baseline is 4. The description adds no specific parameter information because none exist, but it implicitly confirms no arguments are needed.

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?

Description states 'List all active webhook subscriptions' with a clear verb (list), specific resource (webhook subscriptions), and a filter ('active'). It distinguishes itself from siblings like 'get_webhook_subscription' and 'list_webhook_events'.

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 usage for listing active subscriptions but provides no explicit guidance on when to use this tool versus alternatives like 'get_webhook_subscription' for individual subscriptions, or when not to use it. No exclusions or context are given.

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