Toggle Sprint

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

Annotations already indicate idempotentHint=true and non-read-only behavior. The description adds non-obvious behavioral context: sprint state persists until toggled off or the bot stops. This is valuable beyond the schema and does not contradict any annotations.

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 two short sentences with no redundant wording. It is front-loaded with the core action and adds only the essential behavioral detail. 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 simple boolean toggle with solid annotations and no output schema, the description covers the necessary context: what it sets, and how long the state persists. The lifecycle detail ('until toggled off or the bot stops') is complete enough for an agent to understand the tool's effect.

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 only parameter, sprint (boolean), has 0% schema description coverage, but the description compensates by explaining that the parameter controls whether sprinting is on or off. This directly maps true/false to the intended behavior, which is sufficient for a single boolean parameter.

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 specific action: 'Turns sprinting on or off.' It names the resource (sprint) and the behavior (on/off toggle), distinguishing it from sibling tools like minecraft_set_sneak. The added detail about persistence further clarifies the tool's scope.

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 is given on when to use this tool versus alternatives such as set_sneak or jump. There are no exclusions, prerequisites, or contextual hints about when sprinting is appropriate, leaving the selection entirely to the agent.

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