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

With no annotations, the description carries the full burden; it does disclose what the payload conceptually contains (accuracy of final polls, average bias per party), which is more than a bare restatement. However it says nothing about historical coverage, which institutes are included, refresh cadence, or output shape.

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 that front-loads the resource and then the value it provides. It is a noun phrase rather than a verb-led sentence, which slightly weakens the front-loading, but there is no waste.

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?

There is no output schema, so the description must convey the return value, and it does so only at a high level. Missing details about scope (all institutes vs. a subset), time range, and result structure leave an agent able to select the tool but unsure what it will actually receive.

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?

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics for the description to clarify and no schema gap to compensate for.

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 resource (polling institutes) and states the data dimensions returned: final-poll accuracy in past elections and average bias per party. It is clearly distinguishable from most siblings such as get_latest_polls or search_poll_archive, though it doesn't explicitly contrast with the plausibly overlapping get_track_record.

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?

No when-to-use or when-not-to-use guidance, and no sibling is named as an alternative despite get_track_record and get_latest_polls sitting in adjacent territory. Usage can only be inferred from the resource name.

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