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

Annotations already declare the safety profile (readOnly=false, idempotent=true, openWorld=false), so the bar is lower, and the description still adds real substance: one bot per channel, what the bot does (answers DMs, uses channel credentials), and that assignment replaces the existing bot. It omits permission/auth requirements, which is the only 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?

Two tight sentences: the core action is front-loaded, followed by the behavioral detail that matters (replacement and the replacedBotId response field). No filler, no restating of the title.

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 two-parameter mutation with no output schema, the description is nearly sufficient: it covers side effects and even names the replacedBotId return field. It stops short on error/permission behavior and on the social-vs-generic channel boundary.

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% and both parameters (id, botId) are fully documented as UUIDs in the schema, so the baseline of 3 applies. The description adds no format, constraint, or example beyond what the schema already states.

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?

States a specific verb (assign/set) and resource (bot on a social media channel) and explains the one-bot-per-channel model. It does not, however, distinguish itself from the near-identical sibling neuron_assign_bot_to_channel (non-social channel), which an agent must resolve on its own.

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: the description explains the effect of assigning but never says when to prefer this over neuron_assign_bot_to_channel, neuron_unassign_bot_from_social_channel, or neuron_add_bot_channel, nor any prerequisite (e.g. that the channel must exist or be validated).

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