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

With readOnlyHint=true and openWorldHint=false already declared, the description still adds real value: it discloses a privacy rule (course and domain names are never public), that no auth is required, and the semantic of the bot flag. That is genuinely non-obvious behavior beyond the annotations.

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?

A single dense sentence plus one short constraint clause; the returned payload is front-loaded and every clause (contents, privacy rule, auth) carries information. The run-on enumeration is slightly hard to parse but wastes 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?

With no output schema, the description carries the burden of explaining returns, and it does so field by field. The remaining gap is the unresolved overlap with get_town, which leaves an agent unsure which tool to reach for.

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% and both parameters are documented there, including the 'slug' example for city and the pointer to list_regions for regionId. The description adds nothing about either parameter, so the baseline 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 enumerates exactly what the resource holds (rank, % built, biome, districts with building levels, hat tips, bot flag), so an agent knows what it gets back. But it is written as a noun phrase with no verb, and it calls the resource a 'town' even though a sibling tool named get_town exists — the terminology actively muddies which endpoint this is.

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 statement of when to call this instead of get_town, get_region_map, or get_landmark, despite get_town being an obvious near-duplicate. 'No sign-in needed' is access information, not usage guidance, and there is no mention of error conditions or when the bot-flag variant matters.

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