Walk To Player

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

The description adds 'Blocking call' and error conditions (player not found/not loaded, unreachable), which go beyond the annotations. Annotations only cover read-only/destructive/idempotent hints, so the description carries the burden of conveying blocking behavior and failure modes. No contradiction with 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?

Three concise sentences cover purpose, return value, and errors. The description is front-loaded with the main action, and every sentence adds 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?

The return value and error cases are stated, and blocking behavior is noted. However, the 'range' parameter is not described, and there is no elaboration on how the 'near' behavior works. Given the tool's simplicity, this is mostly complete but has a notable gap in parameter semantics.

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 description coverage is 0%, yet the description does not explain the 'range' parameter or the meaning of 'near'. The username is implicitly referenced as 'named online player' but not explicitly mapped to the parameter, leaving the numeric range undocumented.

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 'Paths the bot to stand near a named online player', using a specific verb and resource. It distinguishes from siblings like minecraft_goto_position (coordinates) and minecraft_follow_player (continuous following).

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 use case is implied by 'named online player', but there is no explicit mention of when to use this tool versus alternatives such as goto_position or follow_player. It provides context that it blocks until arrival but lacks exclusionary guidance.

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