Set Setell autonomy mode

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

The description discloses rich behavioral details beyond annotations: explains how each mode handles WARN and FLAG verdicts, mentions atomic correctness guards, and emphasizes operator confirmation. Annotations (idempotentHint=true) are not contradicted and the description adds value.

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, well-structured paragraph with no wasted words. It front-loads the purpose, then explains modes, exceptions, guards, and a usage note. Each sentence contributes 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?

Given the tool's complexity (three modes, effects, requirements, guards) and absence of output schema, the description fully covers what the agent needs to know: mode behavior, prerequisites, and a critical usage guideline about operator confirmation.

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 enums and descriptions. The tool description adds behavioral context for each mode (e.g., TRUST auto-proceeds on WARN with a note, AUTO silently) and notes Business/Pro requirements for TRUST/AUTO, which extends 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?

The description clearly states the verb 'Set' and resource 'autonomy mode for one action class'. It distinguishes from sibling tools like setell_get_autonomy by focusing on mutating the mode. The explanation of modes (WATCH, TRUST, AUTO) provides specific context on what each mode does.

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 clear context for when to use this tool (to change autonomy mode), but does not explicitly state when not to use it or suggest alternatives. It does include a guideline to 'Confirm with the operator before flipping', which adds usage nuance.

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