ask_directions

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

With no annotations, the description carries the full burden. It discloses that the action costs nothing and that NPCs may refuse, but does not explain the result of success (e.g., what information is returned) or any game state changes (e.g., NPC rapport).

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?

Two sentences, highly concise, with the purpose front-loaded in the first sentence. Every word is necessary, no 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?

Given the tool has only one parameter and no output schema, the description is moderately complete. It covers the basic action and cost, but lacks details on success behavior and side effects, which an agent might need.

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?

The single parameter 'npc_key' is not explained beyond its title. The description refers to 'a willing local' but does not connect that to the parameter, nor does it suggest how to obtain the key. With 0% schema description coverage, the description adds minimal value.

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 'points you toward' and the resource 'one street you don't know yet', indicating the tool is for discovering new streets via an NPC. It is distinguishable from sibling tools like 'move' or 'talk_to', though not explicitly.

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 mentions it costs nothing and that withdrawn or hostile NPCs refuse, giving some usage context. However, it does not explicitly compare to alternatives like 'look' or 'move', nor does it state when to use this over other discovery tools.

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