set_crash_time

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

No annotations are provided. The description does not disclose behavioral traits such as whether the change takes effect immediately, persists across reboots, or requires a restart. For a mutation tool with no annotations, this is insufficient 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?

The description is a single, clear sentence that efficiently conveys purpose, constraints, and default. No redundant or filler content.

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 parameter setter with no output schema and no annotations, the description covers the basic purpose and constraints but lacks behavioral context (side effects, persistence, validation details). It is adequate but not complete.

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 schema has 100% coverage with a description of the parameter. The description adds meaningful context by explaining what crash_time represents ('Minimum crash duration before recovery triggers') and the default value, which goes beyond the schema's technical constraints.

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 tool sets the 'crash_time' parameter and defines it as 'Minimum crash duration before recovery triggers.' It provides constraints (UINT16, 100–5000) and a default (500 per profile), making the purpose very specific and distinguishable from other crash-related 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 usage for adjusting crash recovery sensitivity but does not explicitly state when to use this tool versus alternatives like set_crash_delay or get_crash_time. There is no guidance on prerequisites or scenarios to avoid.

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