render_map_ascii

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

The description discloses that the tool works offline without any API, which is a key behavioral trait. It also lists what the output includes (tile layout, event positions, region IDs). However, it does not explicitly state that the tool is read-only or mention any side effects, though such details are not critical for this type of tool.

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 three sentences, front-loaded with the core purpose. Each sentence adds new information: what it does, how it works, and when to use it. No unnecessary words.

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 moderate complexity (4 parameters, no output schema), the description explains the tool's purpose, offline capability, and use cases. It does not describe the output format in detail, but for an ASCII rendering tool, the output is self-evident. It is complete enough for an agent to understand how to use it.

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%, so the baseline is 3. The description adds context by listing what the tool displays, which maps to the 'show_events' and 'show_regions' parameters, but does not provide additional meaning beyond the schema descriptions.

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 uses a specific verb ('Render') and resource ('RPG Maker MV map'), clearly stating the output (ASCII representation). It distinguishes this tool from siblings by specifying it works offline without an API, which is unique among the listed tools.

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 provides explicit usage context: 'Useful when no screenshot is available or you need precise coordinate information.' It does not explicitly state when not to use it or mention alternatives, but the context is clear enough for an agent to decide.

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