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 almost nothing: not whether this is a read-only lookup, what the rating scale/aggregation is, or what the response contains. The only implicit signal is that 'community' distinguishes it from the personal-ratings variant, which is minimal context against a completely empty annotation set.

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 short, but this is under-specification rather than conciseness — no sentence earns its place because there is effectively only a fragment. Being front-loaded is meaningless when there is nothing behind it.

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?

With no output schema and no annotations, the description should at least say what a 'community rating' is or what is returned per region/slug; it does neither. The tool is simple, but an agent still cannot tell this apart from the personal-ratings sibling or predict the payload shape.

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 ('Map slug (e.g. prokhorovka)') and region (enum eu/na/asia, 'Game server region') are both fully documented in the schema. The description adds no format or semantics beyond that, so the baseline of 3 applies.

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 'Map community rating' is a noun phrase that essentially restates the tool name (maps_by_slug_ratings) without a verb or stated output. It gestures at 'community' (as opposed to personal) ratings but never says what is returned or in what form, so it borders on tautology. Sibling tools like maps_by_slug_ratings_me and maps_ratings are not distinguished.

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 maps_by_slug_ratings_me (personal) or the aggregate maps_ratings endpoint. No prerequisites, no region/slug scoping advice, no exclusions are stated. The agent must infer everything from the name.

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