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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it discloses nothing beyond a noun phrase. It does not state authentication requirements, return format, pagination, or what a 'rating' represents, despite 'mine' implying user-specific authenticated data.

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?

The description is extremely short and front-loaded, but its brevity reflects under-specification rather than efficient communication. It provides no structure or content an agent can act on beyond the name.

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 that returns user-specific map ratings, the description is incomplete: it does not explain what ratings are, whether the response is a list or aggregate, or how many results to expect. With no output schema and no annotations, the description should do much more to make the tool safely usable.

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%, so the single region parameter is fully documented in the schema with an enum and description. The description adds no extra meaning, but the baseline of 3 is appropriate when the schema already 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 description 'My map ratings' is essentially a restatement of the tool name maps_ratings_mine. It conveys the resource (map ratings) and scope (mine) but does not state an action or distinguish itself from siblings like maps_ratings (likely all ratings) or maps_by_slug_ratings_me (likely my rating for a specific map).

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 on when to use this tool versus alternatives. The description gives no context, no prerequisites, and no exclusions, leaving the agent to infer usage entirely from the name and sibling list.

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