draw_map_tile

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

No annotations provided; the description lacks any disclosure of side effects (e.g., overwrites existing tiles), permissions needed, or operational details.

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 sentence but is under-specified, omitting necessary detail. It does not earn its place as it provides little beyond the tool name.

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?

With 6 required parameters and no output schema, the description is severely incomplete. It does not mention return values (likely void), dependencies, or constraints like coordinate bounds.

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 only 17% (only 'layer' described). The description 'Draw a tile on the map' adds no meaning to the 6 parameters; it fails to explain their roles or relationships.

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 'Draw a tile on the map' clearly states the action (draw) and resource (tile on map). It distinguishes from siblings like 'create_map' or 'add_actor' but does not elaborate on what 'draw' entails.

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?

No guidance on when to use this tool versus alternatives (e.g., for map editing). It does not mention prerequisites or context such as needing an existing map or tileset.

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