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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about read-only status, pagination, result volume, or whether it requires auth. The word 'community' faintly implies aggregated public data, but that is inference rather than disclosure.

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 short, but it is under-specified rather than concise: a four-word fragment conveys no actionable information. There is no front-loaded verb or scope to anchor the agent.

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?

There is no output schema, so the description should explain the shape of the response (e.g. per-map rating entries for a region), and it does not. For a tool surrounded by many near-identical ratings siblings, this leaves the agent unable to call it correctly or confidently.

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 coverage is 100% with a single enum-constrained 'region' parameter whose description ("Game server region.") already documents it fully, so the baseline of 3 applies. The description adds no further semantics about how region scopes the result.

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 community ratings board" is a noun phrase that essentially restates the tool name maps_ratings; it never says what action is performed (list? fetch? submit?) or whose ratings. An agent cannot distinguish it from siblings like maps_by_slug_ratings or maps_ratings_mine.

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?

No when-to-use guidance, no prerequisites, and no mention of the closely related siblings (maps_by_slug_ratings, maps_ratings_mine, maps_by_slug_ratings_me). The single required 'region' parameter is the only hint that this is a regional aggregate.

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