create_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 of behavioral disclosure. It states the core mutation ('Add a new notification connection') but does not mention whether the connection is validated/tested, whether existing names are overwritten, required permissions, or what happens on failure; a mutation tool with zero annotation coverage needs more than this.

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 sentences with no redundant wording. The operation is front-loaded and the body-building instruction is placed immediately after, so the most actionable information appears first.

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 nested-object creation tool with no output schema and no annotations, the description is adequate but incomplete: it points to get_notification_schema and lists key fields, but it does not enumerate all event toggles, describe the response, or mention validation behavior. An agent may still need to open the schema tool to be fully certain.

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?

Although the schema covers the single config parameter with a generic description, the description adds real semantic value by enumerating required keys (name, implementation, configContract, fields array, and event toggles). This goes beyond the schema and materially helps an agent construct a valid config object.

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 a specific verb ('Add'), names the resource ('notification connection'), and clarifies the scope by noting this is for a new connection, which distinguishes it from update_notification, delete_notification, and test_notification. It also states the source to build the body, removing ambiguity about the tool's role.

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 clearly frames when to use the tool (to add a new notification connection) and provides explicit construction guidance by pointing to get_notification_schema. It does not name alternatives or state exclusions, but the 'new' qualifier plus sibling names make the boundary with update/delete obvious.

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