black_souls_navigate

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

Annotations are minimal (readOnlyHint=false, etc.). The description mentions 'automatic pathfinding over current passability data,' hinting at behavior like obstacle avoidance and map constraints, but does not explain failure cases, timeout behavior, or state changes beyond movement.

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 efficient sentence that conveys core purpose and behavior. However, it could be slightly more informative about parameters without losing conciseness.

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 presence of an output schema (not shown), the description may not need to detail return values. However, it lacks information on preconditions (e.g., must be on a valid tile) and postconditions, which limits completeness for a navigation tool.

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%, yet the description does not explain any parameters (x, y, timeout_ms). The agent must infer that x and y are coordinates and timeout_ms is optional. The description adds no value beyond the schema.

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 verb ('Move'), resource ('target tile'), and method ('automatic pathfinding'). It distinguishes from sibling tools like black_souls_kill or black_souls_input by focusing on navigation.

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 the tool is for movement but does not specify when to use it versus alternatives (e.g., battle actions, interactions). No explicit when-not-to-use context or sibling comparisons.

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