human_mode

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds valuable context beyond them: every process starts disabled, and a mode change cancels in-flight work before returning. It doesn't say whether the cancellation is recoverable or what the query returns, keeping it below 5.

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?

Two short sentences, front-loaded with the query-vs-set choice and followed by the critical behavioral caveat. No wasted 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 one-parameter toggle with no output schema, the description covers usage and the key side effect. The main gap is not describing what the query form returns, which an agent must infer without an output schema.

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 0%, so the description carries the burden for the single parameter. It explains that empty arguments mean query and passing 'enabled' toggles human input, which maps the boolean to intent reasonably well, but it doesn't state the default or explicitly tie true=enable/false=disable.

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 states a specific verb and resource: query the current mode, or explicitly enable/disable human input. This is clear and distinguishable from general status tools like human_status, though it doesn't explicitly name or contrast with its closest siblings (human_pause/human_resume), so it falls short of a 5.

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?

It gives clear when-to-use guidance: call with empty arguments to query, or pass 'enabled' to change the mode. It offers no explicit exclusions or named alternatives for the toggle behavior (pause/resume), so it is not a full 5.

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