os_maps_render

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds the notion of returning metadata and a proxy URL, and hints at overlay contracts and inventory hydration, which is some value beyond annotations but not a rich behavioral portrait. No contradiction exists.

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, dense sentence that front-loads the core purpose (return metadata for static map rendering) followed by additional features. No wasted words, but the technical phrasing could be clearer; still, it is appropriately sized for the complexity.

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?

Although an output schema exists (so return values don't need explanation), the input side is incomplete. The required bbox parameter has no format or ordering details in the schema or description, and size and includeInventory are unmentioned. For a 6-parameter tool with only 1 required param, this leaves an agent uncertain about critical call requirements.

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 33% (only overlays and inventory have brief descriptions). The description mentions 'overlay-ready geometry contracts' and 'os_map.inventory hydration', which adds meaning for those two params, but it does not address bbox, size, or includeInventory. With low coverage, the description fails to compensate for the undocumented 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 returns metadata for rendering a static map image with a proxy URL, and mentions overlay-ready geometry contracts and optional inventory hydration. This is specific enough to distinguish it from raster tile and export tools, though it doesn't explicitly name any sibling differentiators.

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 is provided on when to use this tool versus alternatives. It doesn't mention any context, exclusions, or competing tools like os_maps_raster_tile or os_map_export. The usage context is entirely implied by the description.

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