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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether it is a read-only lookup, not the shape or ordering of the history, not whether the region affects results, not pagination or rate-limit behavior. Three words provide zero behavioral context for a tool with no annotation coverage.

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?

At three words it is not padded, but it is a fragment rather than a sentence and is under-specified rather than concise. Brevity here costs the definition information an agent needs rather than saving anything meaningful.

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, two-required tool with no annotations and no output schema, the definition leaves an agent guessing about return content, ordering, and the relationship to the sibling history/change tools. Only the schema-documented parameters are covered.

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 100%: slug is documented with a concrete example ('prokhorovka') and region is an enum with a description. The description adds no additional parameter meaning, so the baseline 3 applies since the schema does the heavy lifting.

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 fragment 'Map changes history' does convey a resource (map) and an aspect (change history), which is more than a tautology. However it does not distinguish this tool from the sibling maps_changes, and it never states it operates on a single map identified by slug, so an agent cannot confidently separate the two.

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 mention of when to prefer maps_changes (all maps) over this per-slug history, and no prerequisite or context information. Usage must be inferred entirely from the name.

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