İzmir nöbetçi eczaneler (bugün, bölge bazında)

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

Annotations already mark it read-only and open-world, and the description adds valuable context: the İzmir Büyükşehir open-data source, the 'today' scope, and an explanation of the duty note field (e.g., after 24:00). Behavior such as response ordering or absence handling is not disclosed, but with readOnlyHint and openWorldHint present this is sufficient.

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-loads the main content (today's İzmir duty pharmacies) before listing fields and source. The Turkish/English duplication is slightly repetitive but does not bloat the definition materially.

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 one optional parameter, a rich field list, a source note, and an existing output schema, the tool is adequately specified for correct invocation. The only notable gap is the missing explicit statement of behavior when `bolge` is omitted (presumably returning pharmacies for all districts).

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?

The schema covers bolge with a type and example (Bornova, Karşıyaka), and the description contributes the filtering semantics ('`bolge` ile süzme'), which is not explicitly stated in the schema. Together they give the agent enough to pass the parameter correctly, though no formatting or case guidance 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?

The description identifies the resource precisely—today's on-duty pharmacies in İzmir—and lists the returned fields (name, district, duty note, address, phone, coordinates), which makes selection easy. It lacks an explicit verb such as 'list' or 'query', and the differentiation from ibb_nobetci_eczane relies on the city name rather than an explicit comparison.

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?

Clear context is provided: the tool is for today's İzmir pharmacies and supports optional district filtering via `bolge`. It does not explicitly state when not to use it or name alternatives such as ibb_nobetci_eczane, so it stops short of full guidance.

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