fly_to

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

There are no annotations, so the description must disclose behavior. It only mentions 'using creative flight,' which hints at a mechanic but fails to explain side effects, state changes, or requirements. It does not state whether the movement is instantaneous, gradual, or requires the bot to be in creative mode, leaving significant behavioral ambiguity.

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, concise sentence that wastes no words. It immediately communicates the action and the mode of flight, making it efficient and easy to parse.

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 tool is simple with three parameters and no output schema, so the description need not explain return values. However, it lacks mention of any requirements or limitations (e.g., creative mode, command execution context). The description is minimally adequate but not thorough, leaving the agent to infer important context.

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 100%, with each coordinate (x, y, z) described as destination coordinates. The description adds no extra meaning beyond the schema, so the baseline of 3 applies. The description does not clarify coordinate formatting or units, but the schema fully covers the parameters.

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 the tool's function: 'Fly the bot to specific coordinates using creative flight.' It specifies the verb 'fly' and resource 'bot', and distinguishes the mode 'creative flight' from potential alternatives. However, it does not explicitly contrast with sibling tools like teleport_to, so it lacks full sibling differentiation.

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 gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., creative mode requirement) or situations where teleport_to would be preferable. The context implies a movement command but provides no explicit usage guidance.

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