Bot API Chat

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

With no annotations, the description carries the full burden. It implies a two-way interaction but does not disclose whether the tool is synchronous, if it creates a message record, or any side effects. The AI-generated response is mentioned but the response format is not described.

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 two sentences, concise and front-loaded. It states the action and the key requirement without wasted words, though it could be more structured with a usage section.

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?

The tool has no output schema, yet the description says 'receive an AI-generated response' without describing the response structure. The lack of output format details makes it incomplete for an agent to understand what to expect. Also, it doesn't explain that the message is sent to a specific bot via the API key.

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 baseline is 3. The description adds no additional semantics beyond restating the API key requirement. Parameter descriptions in the schema already provide full meaning.

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?

Description clearly states 'Send a chat message to the bot API as a contact and receive an AI-generated response', providing a specific verb and resource. However, it does not differentiate from the sibling tool 'neuron_bot_api_send', which likely has a similar purpose.

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 mentions a requirement ('Requires a valid API key with 'nrn_' prefix') but provides no guidance on when to use this tool versus alternatives like 'neuron_bot_api_send' or 'neuron_send_message'. No when-not-to-use or context exclusions are given.

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