Add Notification

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

No annotations are provided, so the description carries the full burden. It discloses the creation action and type-specific config, but does not mention side effects like whether a test notification is sent, validation behavior, or persistence guarantees. For a mutation tool, this is a notable gap.

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 a single sentence that effectively packs in type-specific examples without unnecessary verbosity. It is front-loaded with the core action and then elaborates with config details, maintaining good readability.

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 has an output schema and full schema descriptions for all parameters, the description's type-specific config examples provide significant supplemental context. It is complete enough for a creation tool, though it could mention the behavior of isDefault/applyExisting in relation to the creation action.

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 coverage is 100%, but the description adds concrete examples for type-specific config fields (e.g., webhookURL for slack, ntfyTopic for ntfy), which goes beyond the generic 'config' schema description. This helps agents construct the config object correctly.

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 'Creates a new notification channel' with a specific verb and resource, distinguishing it from update/delete/list siblings. The title 'Add Notification' is reinforced without tautology.

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 implies usage for creating a notification channel but does not explicitly offer alternatives or when-not-to-use. It provides type-specific configuration guidance, which is a soft usage hint, but lacks explicit exclusions compared to sibling tools.

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