toggle-swim-up-jump-up

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

With no annotations, the description fully discloses the behavior: toggling jump state on/off and the conditional effect when underwater. It adds context beyond the schema by explaining that holding jump (when enabled) causes upward swimming, which is not inferable from the parameter alone.

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 three concise sentences that front-load the primary action, then provide a key conditional behavior, and end with a usage suggestion. Every sentence contributes value without redundancy.

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 one parameter, the description covers the essential behavior: what toggling does, the underwater nuance, and how to control swimming/jumping. It does not mention return values, but given the tool's simplicity and lack of output schema, this is a minor gap.

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 provides 100% coverage for the single parameter 'enabled' with a clear description. The tool description reinforces this meaning but does not add significant new details beyond what the schema states, so it meets the baseline of 3.

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 uses the specific verb 'toggle' and identifies the resource as the bot's jump state, which clearly distinguishes it from siblings like 'jump-in-place' or 'move-horizontally'. It also explains the underwater swim-up behavior, further clarifying its purpose.

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 states 'Use this to control swimming or jumping state,' providing clear context for when to use this tool. It implies that this tool is for maintaining a jump state rather than performing a one-off action, but it does not explicitly rule out alternatives.

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