list_notification_webhooks

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

With no annotations, the description carries the full behavioral burden. It clearly signals a read-only 'List' operation and identifies what is returned, but it does not disclose pagination, ordering, scope behavior beyond the account_id parameter, or error characteristics. This is adequate for a simple list tool but not rich behavioral disclosure.

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 one short sentence with no filler. The verb and resource are front-loaded, making it easy to scan. 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 one-parameter list operation with no output schema, the description is largely complete: it says what action is performed and what resource is returned. It stops short of explaining response shape or pagination behavior, but the tool's simplicity and the schema's full account_id documentation make this a minor gap rather than a critical one.

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%: account_id is documented with type and maxLength. The description adds no new parameter-level meaning, so the schema does the heavy lifting and the description receives the baseline score. It does not repeat the parameter, which is fine.

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 a specific verb ('List') and a specific resource ('configured notification webhook destinations'), so an agent can tell what the tool returns. It does not explicitly distinguish itself from notification siblings like list_notification_policies or list_notification_history, but the resource is named precisely enough that the purpose is unambiguous.

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?

There is no guidance about when to use this tool versus the many sibling notification tools. The description only says what it lists, not why an agent should choose it over list_notification_policies, list_notification_history, or list_available_alerts. Usage context is left entirely to inference.

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