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

Annotations only establish that this is a safe read; the description goes well beyond them by disclosing what the non-image payload contains (page-type counts, link count, unconnected-page count, mapUrl) and, critically, an anti-pattern instruction: do NOT embed the image in a reply because the chat cannot render it. That is exactly the kind of behavioral guidance structured fields cannot carry.

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 usage trigger is front-loaded and the closing instructions are tight, but the long enumeration of every page type and its symbol, plus the full colour-ring legend, is bulky and would be needed only when interpreting a specific image. It earns most of its length but not all of it.

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 no output schema and a single trivial parameter, the description carries the full burden and does so: it explains what the image depicts, what the text block returns, and how the agent should present the result. Nothing needed to call or act on this tool correctly is missing.

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 100% with a single optional 'workspace' parameter, so the schema already documents the token/default-workspace semantics. The description adds nothing about the parameter, so the baseline of 3 applies.

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 states a specific verb+resource ('renders the workspace's visual map to an image and returns it') and the vivid type-to-shape mapping makes clear exactly what the artifact contains. No sibling tool renders a map, so it is trivially distinguishable from compass_pages_list, compass_page_links_list, and the rest.

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 an explicit when-to-use trigger ('when the user asks about the shape of their map, where the problems are, what connects to what, or anything spatial') and pairs it with presentation guidance ('link mapUrl... and describe what you saw'). The routing condition is unambiguous rather than inferred.

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