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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that it both fetches and renders and that the resource must be 'accessible' (implying permission scoping), but it never says what 'render' produces or whether any UI/state side effects occur. That is modest added context, appropriate for a 3.

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 the operation first and the object scope second, and no filler. It is efficient, though the trailing qualifier is more vague than informative.

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 display tool with no output schema, 0% parameter coverage, and no annotations describing returns, the description does not state what the agent gets back (a rendered view, image, URL, or payload) or how the identifier is supplied. The critical unknowns for correct invocation are left unaddressed.

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 0%, so the description must carry the parameters, and it largely does not. It names the resource kinds that already appear as the `kind` enum, but it says nothing about the required `identifier` — its format (ID, slug, path?), how to obtain it, or whether it is scoped per kind. The description adds no meaning beyond the enum the schema already exposes.

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 verb pair (fetch and render) plus the exact resource kinds it operates on (collection, project, map, source), which mirrors the `kind` enum. It is clear on its own, but it never distinguishes itself from heavily overlapping siblings like geobble_map_view, geobble_map_get, or geobble_get, so it falls short of a 5.

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?

The only guidance is the trailing phrase 'for visual inspection,' which implies a rendering use case but does not tell the agent when to pick this over geobble_map_view or geobble_get. With such a crowded sibling set containing two other 'view' tools, the absence of any when/when-not routing is a real gap.

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