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

Beyond the annotations (which declare a non-destructive, open-world write), the description adds substantial behavioral detail: a workspace has one Discord connection holding several channels, each webhook adds a channel, re-sending an existing webhook refreshes it, the first channel is a default channel, and the webhook URL is stored encrypted and never returned. It also describes the return value (connection and added channel with id for platform_settings.channelIds).

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 front-loaded with the core action, then provides necessary user-facing instructions and behavioral context. Every sentence contributes, though the step-by-step Discord navigation is slightly detailed for a tool description and could be trimmed without losing critical information.

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 lack of an output schema and minimal annotations, the description is complete: it covers the return shape, idempotency/side effects, secret handling, and the distinction between adding and refreshing a channel. An agent has everything needed to call the tool correctly and interpret the result.

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 100%, so all four parameters are already documented in the schema. The description reinforces a few points (label defaults to webhook name, workspace_id source, idempotency behavior) but adds little meaning beyond what the structured fields already provide, so the baseline 3 applies.

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 opens with a specific verb and resource: 'Adds a Discord channel to a workspace from a channel webhook URL.' This clearly distinguishes it from sibling tools like list_discord_channels (which lists) and other connection-related tools.

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?

It explains how the user obtains the webhook URL in Discord, notes it works for every channel type including forum channels, and describes what happens when sending an already-connected webhook (refreshes it). It does not explicitly name alternative tools or state when not to use this, but the context is clear enough for an agent to act.

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