List the 81 provinces

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description still adds value beyond them: 'Works offline' confirms no network dependency, and it discloses the payload contents (plate codes and district counts), which matters since there is no output schema. It stops short of describing ordering or total size beyond the count in the title.

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?

Two short, front-loaded sentences with zero waste: the first names the resource and its fields, the second adds the offline property. Nothing irrelevant or repeated.

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 no input params, no output schema and full annotation coverage, the description supplies the essential missing piece, namely what each province record contains. It could go slightly further on ordering or return shape, but an agent has enough to call and use it 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The only caveat is that it doesn't warn there are no filtering options, but none are expected.

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 resource (all 81 provinces of Türkiye) and what each entry contains (plate codes, district counts), which is clear enough for an agent to know this is the enumerate-all tool. It does not explicitly contrast itself with the sibling get_province, so the list-vs-single distinction must be inferred from the plural name.

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 'all 81' wording implies bulk enumeration and the sibling get_province implies a single-lookup alternative, so the routing is reasonably implied. However, there is no explicit statement of when to use this versus get_province or find_district, and no exclusions are given.

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