Verordnungsblätter durchsuchen

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

Annotations (readOnlyHint=true, openWorldHint=true) are consistent with a search tool. Description adds that only Tirol data is available, which is important behavioral context. No contradictions; provides clear read-only nature.

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?

Well-structured with a short summary and bulleted examples. Every sentence earns its place. Could be slightly more concise, but overall 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?

No output schema; description does not explain the result format (markdown vs json) or pagination behavior. While the schema covers input pagination, agents might benefit from knowing output structure. Otherwise, it covers most input aspects.

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 100%, but description adds value with example queries (e.g., 'suchworte="Wolf"') and explains date format and bundesland limitation. This is beyond what the schema provides.

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?

Clearly states the verb 'Search' and resource 'Austrian state ordinance gazettes (Verordnungsblaetter der Laender)'. Distinguishes from siblings like ris_landesgesetzblatt (state law gazettes) by specifying it's for ordinances. The note about only Tirol data provides useful context.

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?

Explains when to use the tool: to find official publications of state/provincial ordinances. Mentions current limitation to Tirol, which guides appropriate use. Does not explicitly exclude alternatives but the context is sufficient.

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