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

Annotations already cover the safety profile (read-only, idempotent, closed-world, non-destructive), so the description is not burdened with basic safety disclosure. It adds meaningful behavioral context by explaining that the output includes red-line pairs with quotes and sources, historical coalition government instances, and the caveat that it is a logic aid rather than a forecast.

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?

The description is front-loaded with the core result: seats and whether the parties reach 61. It then efficiently lists the red-line and historical-government details, followed by a compact caveat. Every sentence adds useful information with no filler.

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 carries the burden of explaining return values, and it does so by naming seats, threshold status, red lines with quotes/sources, and past coalition government elections. It is complete enough for an agent to understand the tool's scope, though it does not specify exact output structure or data freshness.

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 100%, so the schema already documents the parties array and lang enum. The description does not add syntax, format, or selection guidance beyond what the schema provides, so the baseline score of 3 is appropriate.

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 clearly states what the tool returns: seats for a set of parties, whether they reach 61, mutual red lines with quotes and sources, and past coalition government history. It is specific about the resource and operation, but it does not explicitly differentiate itself from siblings such as get_formation or get_formation_history.

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?

Usage is implied by the name and description: use it to test a hypothetical coalition's seats and red lines. The caveat 'A logic aid, not a forecast' gives useful interpretive guidance, but the description never names alternatives or states explicit when-to-use/when-not-to-use conditions versus sibling tools.

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