list_notification_destinations

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'List all' clearly indicates a read-only enumeration operation with no filtering, which is useful, but it does not describe the return shape, pagination, or error behavior. This is adequate for a simple list tool but minimally transparent.

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 only four words and entirely front-loaded. It contains no filler or redundant phrasing, and every word contributes to the meaning.

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?

The tool is simple, with no parameters and no output schema, so the description is minimally viable. However, it omits useful context such as the output structure or the relationship between destinations and channels. An agent could invoke it correctly, but would have limited understanding of what to expect.

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 zero properties and 100% description coverage, so there are no parameters for the description to clarify. For a zero-parameter tool, the baseline is 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 states a specific verb and resource: 'List all notification destinations'. It is clear and unambiguous about the core operation. It does not explicitly distinguish itself from sibling tools like list_notification_channels, but the destination vs channel naming makes the resource reasonably distinct.

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 no guidance on when to use this tool over alternatives such as list_notification_channels or list_alert_policies. There is no mention of context, preconditions, or exclusions, so an agent must rely on the tool name alone.

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