jump-in-place

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

Without annotations, the description is the only source of behavioral info. It only states the action, but does not disclose effects such as whether the bot's position changes, if it's a single jump, or any prerequisites. This is minimal at best.

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 short sentence, which is appropriate for a simple zero-parameter action. There is no wasted text.

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 trivial tool, the description is nearly sufficient, but it fails to distinguish from siblings like 'jump-over-obstacle' or 'toggle-swim-up-jump-up', leaving the agent without enough context to select the correct tool. Slight 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 tool takes zero parameters, so there is nothing to document. The schema already covers 100% (empty properties). The description adds no parameter info, but none is needed.

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 'Make the bot jump' clearly identifies the action (jump) and the subject (the bot). It distinguishes from siblings like 'jump-over-obstacle' and 'toggle-swim-up-jump-up' by focusing on a simple in-place jump, though it doesn't explicitly state 'in place'.

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 usage context is provided. The description does not mention when to use this tool versus alternatives like moving horizontally or jumping over obstacles.

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