get_crash_time

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

With no annotations, the description should clarify behavioral traits. It only provides the parameter range and default, omitting whether the operation is read-only, requires permissions, or triggers side effects. The name implies reading but no explicit statement.

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 concise phrases conveying essential information: what the parameter is and its technical constraints. No redundant words, front-loaded with the purpose.

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?

Covers the basic parameter details but does not explain how crash_time relates to other crash settings or recovery triggers. With many crash siblings, more context (e.g., typical usage or interaction) would improve completeness.

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?

No input parameters exist, so the schema coverage is 100%. The description adds value by explaining the output parameter's data type (UINT16), range (100-5000), and default (500 per profile), which is not present in the output schema (none exists).

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 retrieves the 'crash_time' parameter, defines its purpose as the minimum crash duration before recovery triggers, and provides data type and range. It distinguishes itself from sibling tools like 'set_crash_time' and other 'get_crash_*' 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?

No guidance on when to use this tool versus other crash-related getters (e.g., get_crash_delay, get_crash_dthreshold). The description lacks context about usage scenarios or prerequisites.

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