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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that the response includes a resolved document, hash and expiry; it says nothing about whether the hash changes, whether expiry can invalidate reads, or what 'resolved' means. Minor added value over annotations.

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, listing the return contents up front. It is efficient but so terse that the brevity shades into under-specification.

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 carrying the return summary is helpful, and one required param keeps complexity low. Still missing: the draft lifecycle context (prepare → read → commit), the meaning of 'resolved document', and the relationship to sibling tools, leaving real gaps for a draft tool in a crowded namespace.

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 sole parameter draftId (uuid) is undocumented. The description does not mention draftId at all or explain where a draft id comes from (presumably prepare_map_draft), so it fails to compensate for the schema gap.

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 ('Read') and resource ('map draft') and even names the payload (resolved document, hash, expiry), so an agent knows what comes back. However it does not distinguish itself from the very similar sibling preview_map_draft, nor from prepare_map_draft/commit_map_draft, which weakens selection.

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?

There is no when-to-use guidance, no prerequisite (e.g. that a draft must first exist via prepare_map_draft), and no mention of when to prefer this over preview_map_draft or get_map. The agent must infer placement in the draft lifecycle entirely.

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