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

Annotations already indicate this is readOnly=false, idempotent, not destructive. The description is consistent but adds little beyond stating the basic effect. No contradictions.

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?

One clear sentence plus a list of examples. Front-loaded with the action and purpose. No unnecessary 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?

For a simple toggle tool with no output schema, the description is nearly complete. It explains the effect and gives examples. A minor gap: it doesn't clarify if the change takes effect immediately or requires a bot restart.

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 covers all parameters with descriptions. The description adds value by providing example tool IDs, which helps the agent understand valid values for toolId without requiring external knowledge.

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 the action: toggle a built-in tool on/off for a specific bot. It provides example tool IDs, adding specificity. However, it does not explicitly differentiate from the sibling tool neuron_bulk_toggle_builtin_tools, which could be done by noting it affects a single tool.

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 gives no guidance on when to use this tool vs alternatives like the bulk toggle. It does not indicate prerequisites or situations where toggling is appropriate.

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