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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds a non-obvious and important behavioral fact: secret values are never returned by this operation. The 'list' verb also implies a read-only operation, and nothing in the description contradicts the absence of mutation.

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?

Two short sentences with no filler: the first states the operation and scope, and the second adds a high-value behavioral caveat. 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?

For a simple optional-parameter list tool with no output schema, the description provides the operation, scope, and a critical secret-handling caveat. A more detailed return-shape description would improve it, but the low complexity makes the current description sufficient for correct invocation.

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 100%, so the parameter semantics are already fully documented in the input schema. The description contributes only 'your account', which loosely aligns with the owner_key default behavior but adds no new parameter-level detail.

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 opens with a specific verb, 'List', and names the resource, 'outbound webhook target registrations for your account'. This clearly distinguishes it from sibling tools like register_webhook_target and unregister_webhook_target.

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?

'For your account' establishes the intended scope, and the caveat 'Secrets are never returned again after registration' tells agents not to expect secret values and to capture them at registration time. It does not explicitly name the register/unregister siblings as alternatives, but the context is clear.

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