List Bot Knowledge Bases

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

Annotations are empty, so the description carries full burden. It implies a read-only operation by stating 'Retrieve' but does not disclose any behavioral traits like pagination, rate limits, authentication needs, or response format. It adds value by mentioning 'priorities and metadata' but could be more detailed.

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 concise sentence that immediately conveys the action and result. It is front-loaded and contains no superfluous words.

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 no output schema, the description partially compensates by mentioning 'priorities and metadata' as part of the output. However, it does not specify the structure (e.g., array of objects), order, or error scenarios. The simplicity of the tool (one parameter, no nested objects) makes this adequate but not thorough.

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?

There is only one parameter (id) with a schema description that is already explicit. The tool description does not add any additional meaning or example beyond what the schema provides. With 100% coverage, a baseline of 3 is appropriate.

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 uses the specific verb 'Retrieve' and clearly identifies the resource: 'knowledge bases attached to a specific bot'. It also mentions the output includes priorities and metadata, distinguishing it from siblings like neuron_list_knowledge_bases which list all knowledge bases without bot filter.

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 does not provide any guidance on when to use this tool versus alternatives such as neuron_list_knowledge_bases, neuron_attach_knowledge_base, or neuron_detach_knowledge_base. No context or exclusion criteria are given.

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