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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: ordering ('newest-first'), scope ('caller's'), and provenance ('created via the subscribe tools'). While pagination and return format are not detailed, the essential behavior for a list operation is covered. No contradictions with annotations since none exist.

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 two sentences, with the primary action and scope in the first sentence and a practical usage hint in the second. Every word contributes value, with no filler or repetition of schema content. This is exemplary conciseness.

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 tool's simplicity (list operation, three optional parameters, no output schema), the description covers the key aspects: what is listed, whose, order, and a filtering option. It does not describe the return structure, but with no output schema and straightforward semantics, the provided information is largely sufficient. A 5 would require explicit guidance on expected response shape or pagination behavior.

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 covers all parameter descriptions at 100% coverage, which sets the baseline at 3. The description adds meaningful context by explaining that the listed items are 'rules created via the subscribe tools' and explicitly suggests using `status` for filtering. This enriches understanding of the parameters beyond the schema's bare definitions, justifying a 4.

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 a specific verb ('List') with a clear resource ('webhook subscriptions') and scopes it to 'the caller's'. It also clarifies that these are 'rules created via the subscribe tools', distinguishing it from sibling tools like list_webhook_deliveries and get_webhook. The purpose is immediately understandable.

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 provides clear context by stating it lists the caller's subscriptions and includes a usage hint for the `status` filter. It does not explicitly name alternatives or exclusions, but the sibling tool names (e.g., list_webhook_deliveries) make the differentiation obvious enough. This is one notch below explicit 'when to use vs alternatives' guidance.

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