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

No annotations are provided, so the description carries the full burden and delivers almost nothing: no auth requirements, no error behavior, no note on whether the call mutates state. The presence of an idempotency_key parameter hints at possible side effects on a 'get' action, and the description does nothing to resolve that ambiguity.

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 single sentence is short but not efficient: the parenthetical REST endpoint mapping is the only content and adds no value to an agent that cannot call HTTP endpoints. This is under-specification rather than conciseness.

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 annotations, no output schema, and undocumented parameters, the description must do all the work and does none of it. An agent cannot determine what it receives back or what idempotency_key means, so the definition is not complete enough to invoke reliably.

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 both parameters, so the description must compensate, and it adds no meaning for city_id or idempotency_key. The role of idempotency_key on a retrieval action is especially unexplained.

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 only restates the tool name ("get_district") and maps it to an HTTP endpoint ("identical to POST /api/get_district"). It never states what a district is, what data is returned, or how this differs from get_city or get_map, leaving purpose inferable only from the 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?

There is no guidance on when to call this versus any of the ~30 siblings such as get_city, get_map, or get_turn_packet. The HTTP endpoint mapping conveys no usage context or preconditions.

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