List Notifications

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

Without annotations, the description discloses that credentials are withheld by default and that redacted field names are listed in redactedConfigKeys, providing important security context. It also implies this is a read-only operation, which is useful.

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 focused sentences, no fluff, with the most important information first. Every sentence adds value.

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 list tool, the description covers purpose, usage scenario, and key behavioral detail (redaction). The output schema exists for return structure, and the parameter schema covers includeSecrets, leaving no obvious gaps.

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 sole parameter includeSecrets is fully documented in the schema with security details, so the description adds nothing beyond the schema. Baseline 3 applies because schema coverage is 100%.

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 the specific verb 'Returns' with the resource 'all configured notification channels' and lists examples, clearly distinguishing it from sibling CRUD tools like addNotification/updateNotification/deleteNotification.

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 a concrete use case ('To attach a channel to a monitor you only need its id'), which tells the agent when to call this tool. It does not explicitly mention alternatives or exclusions, so it's one step below the top level.

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