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

Annotations already declare idempotentHint=true and destructiveHint=false, so 'create or reuse' usefully explains what idempotency means here (an existing export may be returned instead of a new one). It also discloses the async nature, which the annotations do not. It says nothing about permissions, quota/rate limits, or what happens if the export is already complete.

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 or redundancy. It is efficient, though it is arguably under-sized for a tool with this much configuration surface, which is captured in contextual completeness rather than verbosity.

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 tool whose inputs are largely a deep nested options tree, with no output schema and no annotations describing the workflow, one sentence is far too thin. The agent is not told how to express view/bbox, that hiddenLayerIds and theme exist, or that it must poll geobble_map_image_export_status to obtain the finished PNG.

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% and the parameters carry real weight: resourceType/resourceId determine the target, and the nested options object controls view (static center/zoom vs bbox bounds), theme, dimensions, layers and overlays. The description names none of these, so it adds no meaning over the raw schema and leaves the agent to parse a large nested object unaided.

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 concrete verb+resource pair ('Create or reuse ... PNG image export') and scopes it to both project and published maps. It implicitly separates itself from the sibling status tool by saying 'prepare', but never names geobble_map_image_export_status, so an agent must infer the pairing.

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 word 'asynchronous' implies this is a job-start call that must be followed by a status check, and 'reuse' implies it is safe to call repeatedly. However, it never states when to prefer this over alternatives or that the status tool is the required follow-up, leaving the workflow to inference.

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