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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds the useful context that only public data is exposed — no personal notebooks, feedback, voice or account data — which is a real scope boundary beyond the annotations, but nothing about catalog size, pagination, or freshness.

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 short sentences, front-loaded with what is listed before the exclusion list. The second sentence is terse but each clause carries distinct scope information; nothing is redundant with the name or annotations.

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 is the only place an agent could learn what a catalog entry looks like (IDs, titles, chart types). It names the content categories but not the shape of the returned list, leaving a gap for an agent that needs to chain into read_public_indicator.

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?

The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. The description correctly does not waste text on parameter talk, though it also never clarifies whether the listing is filtered or complete.

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 ("List") with a specific resource scope: public World Bank indicators plus Election.org civic collections/charts. An agent can distinguish it from read_public_indicator and read_public_civic_records because this is a catalog enumeration rather than a single-record fetch, though the siblings are never named explicitly.

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 personal notebooks, opinions, feedback, voice or account data" gives a clear negative scope, which implicitly signals this is a discovery/listing step rather than a retrieval of specific data. However, it never states when to prefer this over read_public_indicator or read_public_civic_records, so routing must be inferred from the names alone.

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