dokumente suchen

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the search spans titles, Ordnungsangaben and document contents, but says nothing about result limits, ranking, or whether matching is case/accent sensitive.

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 with no filler; the searched-field scope follows the core verb. Nothing extraneous, though it is arguably under-specified rather than maximally efficient.

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 two-parameter read-only search with annotations covering safety and no output schema, the basics are present, but return behavior (result count, ordering, empty-result handling) is absent, leaving gaps an agent would want when calling it.

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 50%: 'frage' is documented with a minimum length, while 'fall' has none. The description's phrase 'eines Falls' at least clarifies that 'fall' scopes the search to one case, partially compensating, but no syntax or format detail is added.

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 (Volltextsuche) and resource (Dokumente eines Falls), plus the searched fields (Titel, Ordnungsangaben, Inhalte). An agent can distinguish it from dokument_text (single-document retrieval), though the description never names a sibling 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?

No when-to-use guidance, no exclusions, and no mention of alternatives such as dokument_text or bestand_pruefen. The agent must infer that this is the entry point for finding documents by keyword.

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