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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context by disclosing that the result is synthesized from multiple sources (elections + forecast + historical correlation), but says nothing about freshness, coverage limits, or what the briefing contains.

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, front-loaded with the resource and scope, with no filler or redundancy. It is slightly jargon-heavy ("election-aware", "joined with") but still compact and information-dense.

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?

For a one-parameter read-only tool with no output schema, the description conveys the core scope and composite nature of the returned briefing adequately. What remains thin is the exact contents/format of the briefing, but the annotations cover safety and the schema covers the input.

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% and the single country_code parameter is documented in the schema with an ISO 3166-1 alpha-2 format and examples. The description adds no parameter-level meaning, 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?

Names a specific output (a censorship risk briefing for a given country) and specifies its distinguishing composition: upcoming elections joined with forecast and historical election-censorship correlation. This differentiates it from siblings like get_upcoming_elections and get_risk_forecast by signaling it is a composite briefing rather than a single-signal lookup.

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?

The description never states when to use this tool instead of the many adjacent siblings (get_upcoming_elections, get_risk_forecast, get_shutdown_risk, get_country_profile). Scope implies usage but no condition or alternative is named, leaving the agent to infer routing.

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