Create Bot

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

Annotations are empty, so the description carries the full burden. It discloses that the tool creates a bot (mutation), but provides no details on side effects (e.g., immediate activation, required permissions, irreversible actions) or response behavior (e.g., success/failure indications). This is minimal for a creation tool.

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 a single sentence, which is concise, but it tries to cover 11 parameters by only listing a few, leading to omission and the misleading 'phone number'. It is front-loaded with the main action but could be restructured to be more accurate and complete without adding length.

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?

With 11 parameters, no output schema, and no annotations, the description is incomplete. It does not mention the return value (e.g., bot ID), or clarify required vs optional parameters beyond implying 'name' and 'system prompt' are included but not emphasizing they are required. It also omits the 'assignment' parameter. For a creation tool, this leaves gaps.

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% (all 11 parameters have descriptions), so baseline is 3. However, the description adds little value beyond listing parameter names ('name, system prompt, and optional parameters like model, temperature, and phone number'). It mislabels 'whatsappChannelId' as 'phone number' and does not clarify relationships (e.g., between 'assignment' and 'responsibilities') or parameter formats (e.g., OpenRouter model ID pattern).

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 'Create a new bot' with specific resources (name, system prompt) and optional parameters. It distinguishes this tool from siblings like 'update_bot' and 'delete_bot' by focusing on creation. However, it refers to 'phone number' which is not a parameter (it's 'whatsappChannelId' as a UUID), causing slight ambiguity.

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?

No guidance on when to use this tool versus alternatives like 'neuron_update_bot' (for modifications) or 'neuron_import_contacts' (for other creation tasks). No prerequisites mentioned (e.g., need an organization or channel). The description implies use for initial bot creation but does not explicitly state when not to use it.

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