Toggle Sneak

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

The description adds behavioral context beyond the annotations: it discloses that sneaking prevents falling off edges and hides the bot's nametag from some mobs. This is useful and not contradictory to the idempotentHint and openWorldHint annotations, though it does not describe server-side effects or response behavior.

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, well-structured sentence that front-loads the verb and purpose. It contains no filler and every word contributes meaning.

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?

Given the low complexity (one boolean parameter, no output schema), the description covers the key behavioral effects and purpose. It lacks explicit when-to-use vs alternatives, but that is a minor gap for a simple toggle tool. The effects mentioned (fall prevention, nametag hiding) enrich the context beyond the schema.

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?

With one boolean parameter and 0% schema description coverage, the description compensates by explaining that the tool turns sneaking on or off, which directly maps to the boolean value (true=on, false=off). It does not explicitly name true/false, but the meaning is clear and sufficient for a single 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 states precisely that the tool turns sneaking (crouching) on or off, with a specific verb and resource. It also distinguishes itself from the similar sibling tool minecraft_set_sprint by detailing unique effects (preventing falls, hiding nametag from mobs).

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 implies when to use the tool (when you want to avoid falling or hide from mobs) but does not explicitly compare it to alternatives like minecraft_set_sprint or provide exclusion criteria. It is usable but not fully explicit.

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