set_standby_mode

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

With no annotations provided, the description carries full burden. It discloses that standby mode monitors VTREF, can automatically reconnect, and restore debug state. This is good transparency, though it does not mention potential side effects or persistence, which would have merited a 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?

The description is extremely concise: a one-sentence summary, a brief technical explanation, and a clear Args section. Every sentence adds value without any fluff.

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 simplicity (one boolean parameter, no nested objects), the description covers the purpose, parameter semantics, and behavioral aspects adequately. The presence of an output schema (even if not shown) supports the brevity of the 'Returns: Confirmation' statement.

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 input schema has 0% description coverage, but the tool description explicitly explains the 'enabled' parameter's meaning: 'True to enable standby mode, False to disable'. This adds clear semantics beyond the schema, which only provides type and default.

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 that the tool enables/disables standby mode for power cycle detection, with specific behavior mentioned (monitoring VTREF, auto-reconnect, restore debug state). It uses a specific verb+resource pair and is distinct from all sibling tools.

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 implies the tool should be used for power cycle detection scenarios, but it does not explicitly state when to enable vs disable, nor does it provide exclusion criteria or alternatives. An agent might need additional context to decide when to trigger this tool.

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