Add a channel

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses the key behavioral trait that the call is inert without confirm: true and that there is no server-side dry run, so the client-side preview is the only safety net. It stops short of describing side effects such as whether the channel is immediately active or how the secret is stored.

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 short sentences, zero filler, with the write-safety constraint front-loaded immediately after the action statement. Every clause carries information the agent needs before invoking a mutating endpoint.

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 write tool with a nested required body and no output schema, the description covers the crucial execution gate but omits what the response looks like on preview versus execution, and what payload shape is expected for slack/email/webhook kinds. It is minimally sufficient rather than complete.

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 a moderate 67%, and the confirm parameter is already fully documented in the schema, so the description's statement about confirm mostly restates structured data. The nested body fields (kind, name, config, secret) and idempotencyKey behavior get no additional meaning from the description, leaving the 'secret' requirement unexplained.

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 gives a specific verb and resource ('Add a channel') plus the underlying endpoint (POST /v1/notification-channels), so the agent knows this creates a notification channel. It is distinguishable from siblings like notifications_updateChannel and notifications_deleteChannel by the 'Add' verb, though it never names those alternatives explicitly.

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?

Usage is only implied: it states the call is not executed unless confirm: true, which effectively tells the agent it must opt in to perform a real write. There is no explicit guidance on when to create a new channel versus updating an existing one, or on preconditions such as required workspace permissions.

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