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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two pieces of context beyond that: the underlying HTTP endpoint and the fact that it is available on every plan ('Her pakette'). It says nothing about response shape, pagination, or error behaviour for an unknown province.

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?

It is short, but that shortness comes from under-specification rather than efficiency: a title fragment, a raw endpoint, and a cryptic two-word note are stitched together without a clear lead sentence. The endpoint is front-loadable context but the particle 'Her pakette.' is unexplained.

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 one-parameter lookup tool with no output schema, the description should at minimum state the identifier format and what the result contains. Neither is given, so an agent knows the endpoint exists but not how to populate `il` or what it will receive back.

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 0% for the single required parameter `il`, so the description must carry the meaning. Embedding `{il}` in the path template weakly signals that it is a path identifier, but it never states whether `il` is a plate code, a province name, or an ID — the one thing an agent most needs to call it correctly.

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 — the districts of a province — and pairs it with the endpoint `GET /v1/konumlar/iller/{il}/ilceler`, so an agent can infer it lists districts for a given province. However, it is a bare noun phrase that largely restates the title 'İlin ilçeleri', with no verb and no mention of how it differs from siblings like `konumlar_iller` or `konumlar_bul`.

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?

There is no when-to-use guidance, no prerequisite (e.g. that a province identifier must first come from `konumlar_iller`), and no exclusions. The trailing note 'Her pakette' refers to plan availability, not to invocation context, so it does not help an agent decide between this and neighbouring location tools.

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