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

No annotations are provided, so the description carries the full burden and fails. The word "feed" weakly implies a read-only, possibly paginated list of changes, but there is nothing about permissions, rate limits, change volume, or result shape. For a tool with zero annotation coverage this is a substantial gap.

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?

Three words is not conciseness but under-specification; there is no fully formed sentence and no useful front-loaded information. It wastes no words, but only because it says almost nothing.

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?

The tool is simple (one enum parameter, no output schema), yet an agent still cannot tell what the feed returns, how far back it goes, or whether results are paginated. The definition is too thin for even this low-complexity operation.

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% — the single region parameter is documented in the schema with its enum values. The description adds no additional meaning about how region scopes the changes feed, so this lands at the documented-schema baseline of 3.

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?

"Map changes feed" essentially restates the tool name with no verb — it never says whether it lists, streams, or retrieves changes. It gestures at a changelog resource but gives no scope, ordering, or time window, and it does nothing to distinguish itself from the nearby maps_by_slug_history or tanks_changes siblings.

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 guidance whatsoever about when to call this instead of maps, maps_by_slug_history, or maps_search. No prerequisites, no exclusions, no alternatives named.

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