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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds two useful pieces beyond that: the resource must be 'accessible' (a permission gate) and the result is rendered for visual inspection rather than returned as raw data. It still says nothing about what happens when the identifier is unknown or the resource is inaccessible.

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?

A single front-loaded sentence with no filler; the verb and resource scope come first. Nothing is wasted, though it is arguably too terse for a two-parameter tool with an undescribed identifier.

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 should clarify what 'render' produces — a visual payload, a URL, an image reference, or a structured view object. That is the main missing piece; otherwise the read-only safety profile and closed-world scope are adequately covered by annotations.

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 0%, so the description must carry the load. It enumerates the four accepted kinds, matching the enum, but the required 'identifier' parameter is never explained — no hint whether it is a slug, numeric ID, or name, nor any format or lookup behavior.

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 gives a specific verb pair ('fetch and render') and enumerates the resource kinds it handles (collection, project, map, source), so an agent knows exactly what it does. It does not differentiate itself from the close sibling map_view, which likely overlaps on the 'map' case, leaving some ambiguity about which to pick.

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?

'for visual inspection' implies this is a read/display path rather than a data-fetch path, and 'accessible' hints at a permission prerequisite. However, no explicit when-to-use, when-not-to-use, or named alternative (e.g. map_view) is given, so the agent must infer routing.

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