black_souls_interact

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

With all annotations false, description carries full burden but only says 'walk up to and interact', not disclosing side effects, whether it changes game state, or what constitutes an event. No mention of movement blocking or confirmation dialogs.

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?

Single sentence, no fluff. Every word adds value. However, it may be under-specified given the tool's complexity.

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 game's many sibling tools and the presence of an output schema, the description is too minimal. It does not specify what happens when no ID is given (nearest event?), what the output represents, or how timeout interacts with the action. Incomplete for an agent to use effectively.

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 0% so description must compensate. Adds meaning for 'event_id' ('optionally selected by ID') but provides no explanation for 'timeout_ms', leaving its purpose unclear despite schema constraints (2000–60000).

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?

Describes a specific verb ('interact') and resource ('event'), and adds 'walk up to' indicating movement. It is clear but does not differentiate from sibling tools like 'black_souls_advance_dialogue' or 'black_souls_battle_action' which are also interactions.

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?

Mentions optional selection by ID, implying use when you want to interact with a specific event. No explicit guidance on when to use this versus alternatives like dialogue or battle actions, leaving context implied.

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