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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description adds real value on top: it states the result is a list of records and explains the cursor-based pagination flow. It stops short of noting ordering or rate limits, but the bar is lower given 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?

Front-loads the purpose, then pagination, then the field list. No filler sentences, though the run-on field enumeration reads as a compressed output schema rather than prose.

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 usefully compensates by enumerating return fields and their types, and annotations carry the safety profile. The main gap is the absence of any guidance on choosing this over the sibling `population` tool.

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 all five parameters are already documented in the schema. The description adds no syntax or filter semantics beyond the schema, so baseline 3 applies. Minor terminology drift: description says 'next_cursor' while the parameter is named 'cursor'.

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 resource (population) and a clear scope (latest year and change since first_year). It's easy to understand what it returns, but it never distinguishes itself from the sibling `population` tool, which likely serves the same resource in a different form.

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 when-to-use guidance or routing against the `population` sibling or `municipal_figures_latest`. The only usage note is operational ('pass next_cursor to get the next page'), which is pagination mechanics rather than tool selection.

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