List Knowledge Base Bots

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, fully covering the safety profile. The description adds the scope (all bots) and the filtering condition, but does not reveal additional behavioral traits beyond what annotations imply. Since annotations carry the burden, a 3 is appropriate.

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 with no unnecessary words. The verb 'Retrieve' is front-loaded, immediately conveying the action. Every word adds value, and the sentence is both concise and clear.

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 simple list tool with one parameter, rich annotations, and no output schema, the description fully explains what the tool does and what it returns (all bots connected to a knowledge base). There is no missing information.

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% with the 'id' parameter described as 'Unique identifier of the knowledge base'. The tool description reinforces this by mentioning 'a specific knowledge base'. No additional semantics are needed beyond what the schema provides, so 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 clearly states 'Retrieve all bots that are connected to or using a specific knowledge base.' It specifies the action (retrieve), the resource (all bots), and the filtering condition (connected to a specific knowledge base). This distinguishes it from sibling tools like 'neuron_list_bots' (all bots) and 'neuron_list_bot_knowledge_bases' (knowledge bases for a bot).

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 explicitly states the use case: when you need bots associated with a given knowledge base. While it does not explicitly state when not to use or mention alternatives, the context of siblings provides natural differentiation. This is sufficient for a simple list tool.

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