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

Annotations already establish read-only and non-destructive behavior, but the description adds substantial context beyond them: it explains the rendered image contents, the text summary fields, how unconnected pages and drafts are drawn, and the critical presentation rule not to put the image in a markdown reply. This is unusually complete behavioral guidance.

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 long but front-loaded and mostly earns its length by explaining how to interpret the visual output and how to present mapUrl. The detailed legend is useful for this visual tool, though some phrasing could be tightened.

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, the description compensates by explaining both return components: the rendered image and the text summary with counts, links, unconnected pages, and mapUrl. It also tells the agent what to do with each, so nothing critical 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?

There is only one parameter, workspace, and schema description coverage is 100%, so the schema already explains its default/override behavior and limitations. The description adds no workspace-specific semantics beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific action (renders the workspace's visual map to an image) and precisely what the result represents: a transit-style map with named tiles, figures, squares, link styles, and regions. It clearly distinguishes this visual/spatial tool from page-listing or search siblings.

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?

Explicitly says when to use it: when the user asks about the shape of their map, where things cluster, what connects to what, or anything spatial. It also tells the agent how to present the result afterward, including linking mapUrl rather than embedding the image.

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