Açık veri portalında veri seti ara

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

Annotations already carry readOnlyHint=true and openWorldHint=true, so the safety and open-world profile are covered. The description adds that this searches across multiple CKAN portals and specific metadata fields, but it does not discuss response behavior, pagination, or portal-specific quirks.

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 compact and front-loaded with the core action, and the bilingual wording improves accessibility. The Turkish and English sentences are partly redundant, but the downstream-call sentence earns its place and the overall length is appropriate.

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 read-only search tool with a full input schema, annotations, and an output schema, the description covers the supported portals, searchable fields, and the follow-up action. It does not need to explain return values in detail because an output schema exists; no critical calling information is missing.

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%, so all parameters are already documented; the description adds useful semantics for `sorgu` by enumerating the searchable fields (başlık, açıklama, kurum, etiketler, dosya biçimleri). It also ties the result field `ad` to the next tool, clarifying how search results should be consumed.

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 opens with a specific verb-resource pair ('veri seti arar' / 'search datasets') and scopes the action to four named municipal portals and the CKAN platform. It also enumerates the searchable metadata fields (title, description, institution, tags, file formats), and the downstream reference to acikveri_veriseti distinguishes this search step from dataset retrieval.

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 instruction 'Sonuçtaki `ad` ile acikveri_veriseti çağrılır' tells the agent what to do after a successful search, routing it to the sibling dataset-detail tool. It clearly names the supported portals, but does not give explicit conditions for when not to use this tool or compare it against sibling acikveri_kayitlar.

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