epl_migel_suche

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

Annotations declare readOnlyHint=true, so description's search nature aligns. Description adds that it returns legal basis and official MiGeL source, providing context beyond the annotation. No contradiction.

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?

Concise: two sentences plus a use_case block. No unnecessary words. Front-loaded with purpose.

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?

Given single required parameter, output schema present, and read-only annotation, the description is complete. It explains purpose, use case, and alternative tool.

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 already describes parameters (suchbegriff, limit, format) with descriptions. Description adds example search terms (e.g., 'Rollstuhl', 'Hoergeraet'), which is helpful but not essential. Baseline 3 due to schema coverage.

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?

Description states 'Suche in der Mittel- und Gegenstaendeliste (MiGeL) nach Medizinprodukten'—specific verb and resource. It differentiates from sibling 'epl_sl_suche' by noting the MiGeL is for medical devices vs medications.

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?

Use case explicitly states: addresses whether OKP covers a medical device, provides legal basis, and directs to 'epl_sl_suche' for medications. Clear when to use and alternative.

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