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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered externally. The description adds genuinely non-obvious result semantics: countries and cities share ONE flat list with no selectable level, and the hierarchy is rolled up so Lagos counts toward both Lagos and Nigeria. That rollup/counting behavior is real value beyond the annotations; only pagination/return-shape detail is absent.

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?

Two densely packed sentences; the flat-list/rollup rule is front-loaded before the filter hand-off. Every clause carries information, though the parenthetical aside makes the first sentence slightly harder to parse than necessary.

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?

No output schema exists, so the description must explain return content — and it does (ranked by count, coordinates where known, flat multi-level list). What is missing is pagination/limit behavior for the 4-param surface, but the core shape an agent needs to call and interpret it correctly is present.

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 75% (limit, country, keyword documented; offset bare). The description adds no parameter-level detail — no syntax hints for `keyword` or `country` matching — so it does not compensate for the undocumented offset. Baseline 3 is appropriate when the schema carries most of the meaning.

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?

States a specific verb+resource ('List every place the research items come from'), plus two distinguishing behaviors: ranked by item count and coordinates where known. An agent can tell it apart from sibling list_* tools (list_institutions, list_subjects) without opening any schema.

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?

Gives an explicit downstream usage path: 'Feed a name straight into the `location` filter of search_research_items.' That is clear, actionable context. It stops short of stating when *not* to use it (e.g. versus list_institutions for organization-based geography), so it misses the top band.

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