ilac_detay

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the data categories returned, which is useful, but says nothing about behavior for an unknown barcode, error handling, or any behavioral constraint beyond what structured fields already convey.

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?

A single well-formed sentence, front-loaded with the action and scoped with 'tek bir', followed by a compact list of what is returned. Every clause 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 an output schema present, return values need not be described, and annotations cover read-only/safety. For a one-parameter lookup the description is nearly complete, missing only barcode format guidance and not-found behavior.

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?

Only one parameter, and schema description coverage is 0% — 'barkod' has no schema description. The description compensates minimally by clarifying it is the barcode used to identify the drug, but gives no format or length expectation. Baseline is 3 given the single-parameter schema.

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?

States a clear verb and resource: fetch a single drug's full details by barcode, and enumerates the field groups returned (license, suspension status, prescription type, essential drug lists). 'tek bir ilaç' implicitly contrasts with the search-oriented sibling ilac_ara, but no sibling is named explicitly.

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 phrase 'Barkodla' implies this is the tool to use when you already have a barcode, distinguishing it from ilac_ara in practice. However, no explicit when-to-use, when-not-to-use, or alternative routing is provided.

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