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 disclose one behavioral trait beyond the name — party names are normalised — and 'latest' implies freshness, but it says nothing about how current the data is, how many polls are returned, or how the limit interacts with the result set.

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?

One tight, front-loaded sentence with no filler. It is a noun fragment rather than a full statement of purpose, but nothing in it is wasted.

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 simple read-only query tool this covers the subject matter, but leaves open what a 'latest' window means and how it relates to the archive sibling. With no annotations and no output schema, a little more behavioral framing would have closed the gap.

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 0% and the single 'limit' parameter (default 20) is not mentioned in the description at all. The parameter name is largely self-explanatory, but the description adds no meaning about what limit counts or what happens by default.

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 resource (latest federal polls / Sonntagsfrage) and adds a data trait (normalised party names), so an agent knows what it returns. It does not explicitly distinguish itself from the closest sibling, search_poll_archive, so it falls short of the top tier.

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 word 'latest' hints at the current-snapshot use case versus search_poll_archive, but the description never states when to use this tool instead of the archive search or whether they overlap. No prerequisites, no exclusions, no explicit context.

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