black_souls_save

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

The description adds value beyond annotations by revealing that the tool injects menu navigation inputs, which is a key behavioral trait. Annotations do not contradict, but the description could further clarify whether the save overwrites the slot.

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, each essential. Front-loaded with the core action and constraint. No redundant or filler content.

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?

While the description provides a critical constraint (Scene_Map) and basic purpose, it lacks explanation of the 'timeout_ms' parameter, error handling if not on Scene_Map, and return value details (though output schema may cover that). Adequate but with clear gaps.

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 only clarifies that the 'slot' parameter is 0-indexed. It does not explain the 'timeout_ms' parameter, leaving it ambiguous. This partial compensation is insufficient for a tool with 2 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 triggers an in-game save to a specific slot by injecting menu navigation inputs. It distinguishes itself from siblings like load and list_saves by specifying the action and the constraint 'Only works from Scene_Map.'

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 indicates the tool only works from Scene_Map, providing a clear usage context. However, it does not explicitly mention when not to use it or provide alternatives (e.g., load for loading saves).

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