disable_speed_limit

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

With no annotations, the description carries full responsibility for behavioral disclosure. It adds only 'auto-wakes if asleep,' which is useful but minimal. It does not mention the PIN requirement, potential failures, reversibility, or the command's asynchronous nature, leaving significant behavioral ambiguity.

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?

A single, front-loaded sentence that communicates the core action and a notable behavior without waste. Every word earns its place.

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 relatively simple command tool with no output schema and fully described parameters, the description is adequate but leaves gaps. It does not clarify whether all parameters are indeed optional (schema says required: 0), especially the PIN, which seems crucial for disabling a safety feature. The auto-wake behavior is mentioned but not elaborated in terms of impact.

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 description coverage is 100%, so the baseline is 3. The description adds no parameter-specific meaning; the schema already explains each parameter. Thus, no additional value is provided beyond the structured fields.

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 action ('Disables Speed Limit Mode') with a specific verb and resource, and the 'auto-wakes if asleep' note adds context. It distinguishes well from the sibling tool enable_speed_limit.

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 use case is implied (disabling speed limit mode) but there is no explicit guidance on when to use it versus alternatives, no prerequisites, or exclusion criteria. The 'auto-wakes if asleep' hint does provide some context but not enough to fully guide the agent.

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