gta-render-map

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

With no annotations, the description carries full burden. It discloses offline rendering, base map usage, and inline image return, but omits potential side effects like file size or performance constraints.

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?

Three sentences, front-loaded with key info (offline, marker drawing, inline image). No wasted words; every sentence adds value.

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?

The description covers offline rendering, coordinate ranges, and input modes. It lacks mention of output format/size and mutual exclusivity of category/points, but overall is sufficient for a rendering tool with no output schema.

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 is 75% (3 of 4 params described). The description adds context about coordinate ranges and two input modes, but does not clarify mutual exclusivity of category and points, nor add detail for the undocumented title parameter.

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 renders a GTA Online map image offline, draws markers from bundled or custom coordinates, and returns an inline image. It distinguishes from siblings like gta-map-locations by specifying offline rendering and direct image output.

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 clear context for when to use (offline map rendering) and gives coordinate ranges, but does not explicitly exclude alternatives or specify prerequisites, leaving some ambiguity.

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