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

The description adds value beyond annotations by stating it 'replaces any previously assigned bot', which complements the idempotentHint=true and destructiveHint=false. It does not contradict annotations and provides useful behavioral context, though it could mention prerequisites like channel existence.

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 concise: two sentences, 16 words total. It is front-loaded with the verb and action, and every sentence contributes meaningful information. No waste.

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 simplicity (two params, no output schema), the description covers the key operation and replacement behavior. It is mostly complete, but could mention that the action is idempotent (though annotations cover that) or what happens after assignment (e.g., confirmation). Still, it provides adequate context for an agent to use the tool.

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%, so the baseline is 3. The description rephrases the parameters but does not add semantic details beyond what the schema already provides (e.g., UUID format). It supplies context for the overall operation, but not parameter-specific depth.

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 the action ('Assign'), the resource ('bot to handle incoming messages on a specific WhatsApp channel'), and includes a critical behavioral note ('Replaces any previously assigned bot'). This distinguishes it from related siblings like 'unassign_bot_from_channel' and 'assign_bot_to_social_channel'.

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 when to use (for assigning a bot to a WhatsApp channel) and notes the replacement behavior, but does not explicitly list alternatives or when not to use it. The context is clear, but lacking direct exclusions or comparisons to other tools.

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