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

Annotations already flag destructiveHint=true and openWorldHint=true, so the agent knows this is a risky, world-affecting mutation. The description adds useful reassurance that control is retained and the behavior is stoppable, but it does not disclose what autonomy actually risks (combat, death, resource use, persistence across sessions), which is the key behavioral question for a destructive toggle.

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 compact sentence that front-loads the 'on:' case and then the 'off:' case, with no padding. Slightly terse for a destructive action, but nothing is wasted.

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 one-parameter toggle this covers the basics, but given destructiveHint=true and no output schema, the definition should say what autonomy exposes the character to and how stopping behaves. It is callable as written, but an agent lacks the risk context needed for confident invocation.

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 coverage is 0%, so the description must carry the boolean's meaning, and it does: it defines both the 'on' state (self-directed hunting) and the 'off' state (idle waiting). That is essentially full semantic coverage for the single parameter, with only the persistence/stopping mechanics left unclear.

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 makes clear this is an autopilot toggle: 'on' means the character hunts by itself, 'off' means it stands still. The verb is implied rather than stated, but the behavioral outcome is specific enough that an agent can distinguish this from direct-control siblings like game_command or go_to.

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 intent is implied — use it when you want the character to act autonomously — but there is no explicit statement of when to use it versus issuing direct commands, and no mention of when not to. Adequate but leaves routing to the agent's inference.

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