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

No annotations are provided, so the description carries the full burden. It does add one real behavioral trait beyond the name — that results are volatile and partial ('results so far') and that output is framed as a deviation from the forecast. It says nothing about update cadence, availability outside election night, or what happens for a non-live election id.

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 compact sentence with the scoping cue ('Election night') front-loaded and the returned measures enumerated tersely. No wasted words, though the fragment style carries no supporting detail.

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 annotations and no output schema, the description is the only guidance an agent has, and it omits the sole parameter's semantics, error behavior, and update/freshness expectations. It describes what comes back but not enough to invoke the tool correctly or know when it will return nothing useful.

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 required parameter, election_id, with 0% schema description coverage, so the description must compensate and does not. It never mentions the id, its expected form, or whether it must reference a currently live election, leaving the only input entirely undefined.

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 names the resource and its scope precisely: live election-night figures — counted share, turnout, running results, and deviation from forecast. 'Election night' clearly separates it from aggregate siblings like get_election_statistics and get_latest_polls, though it never names an alternative explicitly and is a noun phrase rather than a verb+resource statement.

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 'Election night:' prefix implies the temporal window in which this tool is appropriate, which is genuine (if implicit) usage guidance. It gives no exclusions, no preconditions, and no routing to alternatives such as get_election_statistics or get_constituency_results for non-live queries.

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