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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only lookup, what happens for an invalid or foreign postcode, or — critically in Germany — whether a postcode can map to more than one constituency and how ties are resolved.

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 short clause with zero filler, and the key qualifier ('German postcode') is present immediately. It is a fragment rather than a sentence, which is acceptable at this size.

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 one-parameter lookup with no output schema, the description should at least indicate what is returned (single constituency vs. list) and how ambiguous postcodes behave. Those gaps are modest but real, so this is only minimally viable.

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 coverage is 0%, so the description must compensate. It adds that the postcode is German, which is meaningful context beyond the bare 'Postcode' string property, but it gives no format or validation detail (length, leading zeros, numeric-only).

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 a specific resource (Bundestag constituency) and a specific input (German postcode) and states the mapping performed, so an agent can tell it apart from siblings like get_constituency or get_constituency_dossier. It is phrased as a noun clause rather than a verb, but the semantics are unambiguous.

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 guidance on when to use this lookup versus get_constituency, get_constituency_race, or get_constituency_results. The only implied usage is 'you have a postcode', which the schema already conveys.

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