set_crash_dthreshold

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

With no annotations, the description carries full burden for behavioral transparency. It provides the units, range, and default value, but does not disclose whether the change takes effect immediately, requires a reboot, or any side effects. The description lacks behavioral context beyond the parameter definition.

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 sentence with two clear parts: the action and the parameter specification. It is efficient, front-loaded with the purpose, and contains no extraneous 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 simple configuration setter with one parameter, the description is mostly complete: it gives the parameter's role, units, range, and default. It does not explain how this threshold interacts with other crash detection parameters, but such detail is not strictly necessary for a standalone setter.

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 already describes the parameter as 'Value for crash_dthreshold (UINT16, 10–2000)' (100% coverage). The description adds semantic meaning ('D-term threshold above which crash is detected'), units (deg/s2), and the default value (50 per profile), which goes beyond the schema's minimal description.

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 this tool sets the crash_dthreshold parameter, which is the D-term threshold in deg/s2 for crash detection. The verb 'Set' is explicit, and the resource is named precisely, distinguishing it from other crash-related parameters like crash_gthreshold.

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 does not explicitly state when to use this tool versus alternatives like set_crash_gthreshold or set_crash_time. However, as a simple parameter setter, the usage is implied: to configure the crash detection sensitivity via the D-term threshold. No exclusions or when-not-to-use guidance are provided.

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