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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds useful behavior: newest-first ordering, cross-parliament scope, and the important counting rule that fraktion refers to the introducing caucus, not the answering government. It does not describe pagination or response/error behavior, but the core behavioral context is strong.

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?

The description is compact and front-loaded: first the resource and ordering, then an example, then parameter-by-parameter semantics. Every sentence adds usable information without repetition.

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 six-parameter search tool with no output schema, the description covers scope, ordering, filtering, and all parameter meanings thoroughly. It could mention result structure or pagination behavior, but nothing essential to invoking the search correctly appears missing.

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?

With 0% schema description coverage, the description fully compensates by defining all six parameters: suchbegriff prefix/all-words matching, parlament allowed values and empty behavior, fraktion accepted abbreviations and counting semantics, art examples, seit date format, and anzahl range 1–50. This is exactly the parameter meaning an agent needs beyond the bare schema.

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 clearly states a specific search operation over Drucksachen from Bundestag and Landtage, cross-parliament, newest first, and gives an example. It does not explicitly differentiate this search tool from siblings such as drucksache (singular) or vorlagen_suchen.

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 example use case implies a search/list scenario, but the description does not explicitly say when to use this tool versus siblings like drucksache or vorlagen_suchen. Use is inferable but not guided.

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