Search Mevzuat

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and an output schema exists, so the safety profile is covered. The description adds only the workflow handoff to get_mevzuat_content; it says nothing about result ranking, semantic reordering behavior, or how empty keyword searches behave across the ten filters.

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?

Two short sentences, zero filler, with the core purpose front-loaded and the follow-up action second. Nothing is wasted and the agent can parse the intent immediately.

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 ten-parameter tool, the description covers the primary input modes and the required follow-up call, while the 100%-covered schema and existing output schema carry the remaining detail. The main gap is the absence of any note on pagination or result volume, which the page parameter implies but the description never addresses.

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 the schema already documents every parameter including the type enum list and date formats. The description's mention of 'kanun no, ad veya metin' loosely maps to mevzuat_no, mevzuat_adi, and phrase, but adds no syntax or semantic detail beyond the schema — baseline 3 applies.

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 names a specific verb and resource ('Mevzuat ara') and enumerates the three lookup modes: statute number, name, or full text. It partially differentiates from siblings by routing follow-up lookups to get_mevzuat_content, though it doesn't distinguish itself from search_within_mevzuat or search_emsal beyond that.

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?

It gives a downstream workflow hint ('Sonra mevzuat_id ile get_mevzuat_content kullan'), which implies this is the entry-point search. However, it offers no explicit when-to-use versus the nearby search_within_mevzuat, get_mevzuat_madde_tree, or search_emsal tools, so usage is only implied.

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