Get Bot

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

The description implies a read-only operation (retrieve info), which is appropriate for a get tool. However, with no annotations provided, it does not explicitly disclose behavioral traits like idempotency, rate limits, or authentication needs, leaving some ambiguity.

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, clear sentence with no unnecessary words. It efficiently conveys the purpose and scope without redundancy.

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 the low complexity (1 required parameter, no output schema), the description adequately summarizes the output contents. It could mention the return format, but the provided detail on configuration, status, and resources is sufficient for most use cases.

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?

The schema provides full coverage for the only parameter 'id' with a clear description. The tool description adds no additional meaning beyond the schema, so the baseline score 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 specifies the action (Retrieve), the resource (bot), and the scope (by ID, including configuration, status, and associated resources). It distinguishes from sibling tools like neuron_get_bot_analytics and neuron_list_bots by focusing on detailed information of a single 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 provides no guidance on when to use this tool versus alternatives (e.g., neuron_list_bots for listing all bots). It lacks explicit context for selection or exclusions.

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