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

With no annotations, the description carries the full burden, and it does disclose useful behavioral context: the publication source, the changing monetary threshold, and the historical coverage start. However, it never states pagination behaviour despite a limit parameter defaulting to 50, nor whether 'totals per party' means aggregated rows mixed with itemised records, which is a real ambiguity.

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 dense sentence that front-loads the resource and scope before listing returned fields; no filler sentences. Slightly overloaded with parentheticals, but every clause carries information.

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 four-parameter tool with no annotations, no output schema, and zero schema-level parameter documentation, the description should cover parameter meaning and result shape. It covers the data domain well but leaves filtering semantics and pagination entirely to inference.

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% across four parameters (year, limit, party, from_date), so the description must compensate and largely does not. It alludes to dates and years only through the data-coverage narrative and never explains what 'limit', 'party', or 'from_date' accept or how they interact.

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 (large donations to German parties), its publisher (Bundestag), and the exact inclusion threshold (35,000 euros, previously 50,000), plus the fields returned. That is far more precise than the bare name. It does not, however, differentiate itself from any sibling, though the sibling list is largely unrelated domains.

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?

There is no statement of when to use this tool versus an alternative, nor any prerequisite. The threshold and coverage dates ('itemised since 2009') imply the data's scope but do not tell the agent when this tool is the right choice.

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