Bezirksverwaltungsbehörden durchsuchen

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds valuable context about geographic coverage limitations but does not detail pagination behavior or result structure beyond the schema. No contradictions.

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 highly concise with no redundant sentences. It front-loads the purpose, then gives usage notes and examples. Every sentence earns its place.

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?

With 11 parameters fully described in the schema and strong examples, the description is complete enough for an agent to use effectively. No output schema exists, but the response_format parameter clarifies the output type. The description could mention pagination behavior, but given annotations, it is sufficient.

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 100%, so baseline is 3. The description adds value by providing example queries that demonstrate how to use parameters like bundesland, suchworte, and bezirksverwaltungsbehoerde together, which is not obvious from the schema alone.

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 explicitly states the tool searches Austrian district administrative authority announcements, provides the German name, and includes example queries that clarify the scope. It differentiates from sibling tools by specifying this particular authority type.

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 description explicitly states when to use this tool (for district administrative authority announcements) and notes that only certain states publish here, helping the agent avoid ineffective searches. It also provides example queries showing proper parameter combinations.

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