render_map

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

No annotations are provided, so the description carries the full burden. It mentions rendering to an image file but lacks details on behavioral traits such as file format (e.g., PNG, JPEG), overwrite behavior, permissions needed, performance implications, or error handling. This leaves significant gaps for an agent to understand how the tool operates beyond the basic action.

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, efficient sentence that front-loads the core action and key details (output to image file, specified dimensions). There is no wasted verbiage, making it easy to parse and understand quickly.

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 complexity of a rendering tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It lacks information on output format, error conditions, dependencies (e.g., requires a loaded project), and behavioral nuances, leaving the agent with insufficient context to use the tool 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 description coverage is 0%, so the description must compensate. It adds meaning by specifying that parameters relate to 'dimensions' (width and height) and output 'path', but does not explain semantics like path format (absolute/relative), width/height units (pixels), or constraints (e.g., min/max values). This provides some context but falls short of fully documenting the 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 action ('Render') and resource ('current map view to an image file'), specifying the output format and purpose. However, it does not explicitly differentiate from sibling tools like 'save_project' (which might save project files) or 'get_project_info' (which retrieves metadata), leaving some ambiguity about when to choose this tool over others for image-related tasks.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing an open project or active map view), exclusions, or comparisons to siblings like 'save_project' for saving images or other rendering methods. Usage is implied but not explicitly defined.

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