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

With no annotations, the description carries the full burden, yet it only implies a personal/authenticated scope through the word "My". It does not disclose auth requirements, what happens when the user has not rated the map, or whether this is a read-only lookup.

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?

It is a single five-word fragment with zero waste, but that brevity comes from under-specification rather than disciplined editing. The key scoping fact (personal rating) is present but nothing else is.

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 name implies authenticated personal data, with no annotations and no output schema, the description omits auth context, empty-result behavior, and what the rating payload contains. It is too thin for an agent to call it confidently in edge cases.

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% with both region and slug documented and region enumerated, so the schema does the heavy lifting. The description adds no format, defaults, or clarifying detail beyond the schema.

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?

"My rating of this map" identifies the resource (a map rating) and implies user scoping via "My", which loosely separates it from maps_by_slug_ratings. However it is a bare noun phrase with no verb and reads as a restatement of the tool name rather than a statement of what the tool does or returns.

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 the sibling maps_by_slug_ratings or maps_ratings_mine, and no hint that an authenticated user context is required for a "my"-scoped call. An agent must infer all routing and prerequisites.

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