set_crash_recovery

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

No annotations provided. The description does not disclose side effects, such as whether the change is immediate or requires reboot, whether it can be set while armed, or how it interacts with other crash settings. Minimal behavioral context beyond the value options.

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?

Description is concise and front-loaded with the action. It uses a compact format to list options and default. However, the use of brackets and abbreviations slightly hinders readability.

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 single-parameter setter with no output schema, the description is fairly complete but lacks context on when to use each option and behavioral implications. Given many related crash settings, it does not fully stand alone.

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% (1 param). The description adds meaning by listing allowed string values (BEEP, DISARM) and default (OFF), which goes beyond the schema's generic 'UINT8' description. However, it does not map these strings to numeric values or clarify if other numeric inputs are valid.

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?

Description clearly states it sets crash_recovery and explains the allowed values BEEP and DISARM and the default OFF. It differentiates from sibling tools like get_crash_recovery by being the setter, but does not explicitly distinguish from other set_* tools. However, the purpose is specific and clear.

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?

No guidance on when to use this tool vs alternatives, when to choose BEEP vs DISARM, or any prerequisites. The description lacks explicit when/when-not recommendations.

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