Bulk Toggle Built-in Tools

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

Description is straightforward but lacks details on side effects, reversibility, or permissions needed. Annotations only provide openWorldHint, so more behavioral context (e.g., 'This updates the bot's tool configuration') would improve transparency.

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?

Single sentence, front-loaded with purpose, no extraneous words. Efficiently communicates the essential information.

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 operation, the description covers what the agent needs: target bot ID and settings. Missing return value info, but no output schema exists and the action is straightforward.

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. Description adds a useful summary of the settings array structure ('array of { toolId, enabled }'), but does not provide new meaning beyond the schema.

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?

Clearly states the action (enable/disable), resource (built-in tools for a bot), and scope (multiple at once). Distinguishes from sibling 'neuron_toggle_builtin_tool' by noting bulk operation.

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?

Implicitly indicates usage for multiple tools via 'at once' phrasing. Does not explicitly state when not to use or reference the single-toggle alternative, but the name and context make it clear enough.

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