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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered elsewhere. The description contributes the useful detail that the return is a 'full map specification' (complete snapshot rather than a diff or summary), but says nothing about behavior on invalid or nonexistent versions.

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 historical qualifier lands immediately after the resource. Nothing to trim and nothing buried.

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 two-parameter read-only tool with no output schema, the description covers the essentials of what is returned ('full map specification'), but leaves the nested input object and version-selection mechanics undocumented. An agent could call it, but would have to open the schema to learn how versions are discovered.

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 reported at 0%, so the description must carry parameter meaning and it largely does not — 'prior version' only obliquely gestures at the version parameter and never mentions projectId. Neither the accepted version range nor the 'use the history list to see available versions' guidance appears in the description.

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?

Specific verb ('Read') plus a precisely scoped resource ('full map specification of a project as it was at a prior version'), which clearly separates it from live-view siblings like map_view or project_update_settings. It does not name any sibling explicitly, so differentiation is by inference rather than statement.

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 phrase 'as it was at a prior version' implies the use case (historical inspection) but never states when to prefer this over the current-state view, nor any prerequisite such as needing a version number from a history listing. That hint exists only in the schema's version field, not in the description.

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