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

Annotations indicate readOnlyHint=true, which aligns with a read operation. The description adds valuable behavioral context: secrets are never returned on reads, only shown at creation/rotation. It also details the exact structure of responses for both modes, going beyond 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 three sentences, each serving a clear purpose: stating the overall function, detailing output without id, detailing output with id, and an important security note. It is front-loaded, efficient, and contains no unnecessary words.

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 complexity (two modes, delivery logs, secrets handling), the description covers all necessary aspects: purpose, parameter usage, response structures, and security behavior. There is no output schema, but the description adequately describes return values.

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 input schema has 100% coverage for the single parameter 'id' with a description. The tool description adds further meaning by explaining the behavioral difference between omitting and providing the id, which enriches the semantic understanding beyond the schema's static description.

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 the tool lists outbound webhook subscriptions, with two distinct modes: without an id returns a list with specific fields; with an id returns the subscription plus recent deliveries and attempts. It also distinguishes itself by noting secrets are never returned. This is specific and differentiates from sibling 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 provides clear guidance on when to omit the id (to list all) and when to pass an id (to get a specific subscription with logs). It does not explicitly mention alternatives or when not to use the tool, but the guidance is sufficient given no similar sibling tools.

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