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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world). The description adds real behavioral context beyond that: each returned value carries its own period, and the answer names the source and licence, which tells the agent to expect provenance metadata and potentially mixed periods. It does not discuss rate limits, error conditions, or pagination beyond what the schema states, keeping it at a solid 4.

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 sentences, front-loaded with what gets ranked and by what, then scope, then provenance and code-sourcing. Dense but every clause carries information; only the parenthetical topic restatement is mildly redundant with the schema.

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 must characterize returns — it does so by stating that values carry their period and that the source and licence are named. Combined with the annotation-covered safety profile and fully documented schema, an agent has enough to invoke correctly; only result-shape details (e.g., ordering guarantees, empty-result behavior) are absent.

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 the baseline would be 3. The description goes further by explaining the interplay between indicator and topic ("news_topic_share:<topic>", or pass topic separately) and by naming list_map_apps as the source of valid indicator codes, adding meaning beyond the per-property schema text.

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 states a specific verb (rank) and resource (countries/US states/counties/congressional districts) drawn from a named data source, and scopes the ranking to a single indicator. An agent can immediately distinguish this ranked-list tool from siblings like get_statistic or find_places without opening the 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?

It gives clear context: ranking over the latest or a chosen period, optionally narrowed by within, and it routes the agent to list_map_apps for indicator codes. It also gives an explicit alternative form for news-topic indicators (indicator carries the topic or pass topic). It stops short of naming a sibling as the wrong tool or stating exclusions, so it is a strong 4 rather than a 5.

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