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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so safety is covered; the description goes further by disclosing that the image is returned inline, that a reusable image URL is also returned (requiring the caller's own key), and that each call consumes one static image against a monthly cap. That quota/credential context is exactly the kind of thing annotations cannot express. It stops short of saying what happens when the cap is exhausted or how errors surface, which keeps it off a 5.

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?

Four sentences, front-loaded with the core action, then modes, then cost, then the exclusion — a sensible ordering with no filler. The stacked parentheticals in the opening sentence ("(returned inline)", "(markers)", "(path, e.g. a route)") are slightly cluttered but each carries disambiguating information.

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?

For a 10-parameter, zero-required rendering tool with no output schema, the description covers what is produced (inline image plus reusable URL), how the viewport is resolved, and the cost model — enough to call it correctly. The remaining gap is precedence when both center/zoom and markers/path are supplied, which an agent must currently guess.

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 100%, so the baseline is 3, but the description adds meaning the schema cannot: the relationship between center/zoom and markers/path (viewport is auto-fitted when no center is given) and that padding governs that auto-fit. It adds no per-parameter detail beyond the schema, which is appropriate here.

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?

"Render a map as an image" is a specific verb+resource, and the description immediately enumerates the payload (optional pins/markers, a line/path) and the output form (returned inline). It also names the sibling it is not for (privacy_area_map), so an agent can distinguish it from geocode, reverse_geocode and map_setup without opening a schema.

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?

It gives explicit operating modes — "Give center and zoom, or just markers and/or path and the view is fitted automatically" — plus a hard exclusion with a named alternative: "Do not use this to show a private address such as someone's home; use privacy_area_map instead." Both when-to-use and when-not-to-use are stated rather than inferred.

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