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

No annotations, so the description carries the burden. It usefully discloses the breadth of the aggregated payload, which sets expectations for a large multi-domain response. However, it says nothing about read-only safety, cost, rate limits, or pagination for what is clearly a heavy aggregation call.

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 front-loaded sentence leading with 'Everything on one Bundestag constituency in one call', then enumerating contents. Dense but every clause maps to a real returned domain, so little 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 broad aggregation tool with no annotations and no output schema, the content enumeration is the right instinct and mostly sufficient to set payload expectations. It falls short on parameter format and on routing the agent between this and the narrower constituency siblings.

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?

One parameter ('number') with 0% schema description coverage, so the description must compensate. 'One Bundestag constituency' plus the self-describing name 'number' conveys that it is the constituency number, but no format or range (e.g. Wahlkreisnummer bounds) is given.

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 verb ('get') and resource ('one Bundestag constituency') and enumerates the payload domains (structure, postcodes, results, forecast, members). The phrase 'everything... in one call' implicitly contrasts it with the leaner get_constituency/get_constituency_results siblings, but no sibling is named explicitly.

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 'everything... in one call' — the agent can infer this is the comprehensive option versus the narrower constituency siblings — but there is no explicit when-to-use/when-not guidance or named alternative for a partial lookup.

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