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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely new behavioral context: only recommendations backed by at least one feed source that nothing contradicts are surfaced, and declarations are restricted to those made before the consultations — this tells the agent how trustworthy and how current the data is.

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, correctly front-loaded with the scoping clause 'Where forming the government stands:' followed by the payload list. Every listed item is substantive rather than filler, though the colon-and-list construction is slightly heavy for one sentence.

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 item by item (stage, recommendations, declarations, mandate, deadline). Combined with annotations that cover the read-only/idempotent profile and a fully documented single parameter, an agent has enough to call it correctly; only the current-vs-historical boundary is left implicit.

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?

There is a single optional parameter with 100% schema description coverage and an enum, so the schema fully documents it. The description adds nothing about language behavior or defaulting, so the baseline of 3 for high coverage 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?

The verb-plus-resource is implicit but unambiguous: 'Where forming the government stands' names the exact subject and then enumerates the payload (stage, confirmed recommendations, leaders' declarations, mandate and deadline). An agent can tell it apart from get_formation_history and check_coalition by the current-state framing, though the description never explicitly contrasts them.

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 only implied — an agent infers it should call this when it needs the present state of government formation. There is no explicit when-to-use or when-not-to-use statement and no mention of the sibling alternatives (get_formation_history, check_coalition) that an agent might confuse it with.

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