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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds genuinely useful non-schema context: refresh cadence ('Updated twice a day'), billing cost and plan eligibility, the endpoint path, and that the payload is JSON in Turkish with `source` and `guncelleme` fields. It does not discuss error behavior or unit/format conventions beyond that, keeping it at a 4 rather than 5.

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?

Front-loaded with the payload description before operational metadata, and two compact blocks with no filler. The endpoint/plan/cost sentence is dense but each element (endpoint, plan availability, unit cost) is decision-relevant for an agent. Slightly over-packed for a one-parameter tool, keeping it from a 5.

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?

There is no output schema, so the description carries the return-value burden and does so well: national average plus top/bottom five, per-province fill percentages with measurement dates, source and update timestamp, Turkish JSON. Combined with the refresh cadence and cost note, an agent has everything needed to call and interpret this correctly.

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% and the schema already explains that `il` accepts a province name or plate code and that omitting it yields the national summary. The description restates that behavior and adds only the shape of the province-level output (fill %, measurement date). With the schema doing most of the work, this is the expected baseline of 3.

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 specific verb and resource ('Returns the Turkey-wide average dam fill rate and the five fullest and emptiest dams') and then explicitly adds the province-scoped variant when `il` is supplied. No sibling tool covers dam reservoirs, and the national-vs-provincial split is spelled out, so an agent can identify this tool immediately.

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?

Gives clear selection logic: omit `il` for the national summary, pass `il` to get that province's dams. It also discloses the availability and cost conditions ('Available on all plans, including free. Costs 1 request unit per call'), which helps an agent decide whether to call it. It stops short of naming any alternative tool or stating when not to use it, but no real sibling alternative exists for this data.

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