get_city_districts

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It does not state whether the tool is read-only, any side effects, rate limits, or return format. The pagination parameters hint at behavior, but the description does not disclose what happens with results or how the search radius affects output.

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 description is concise and well-structured as an Args list. The purpose statement is front-loaded, and each parameter is given a brief, useful explanation without unnecessary prose.

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?

The description covers all parameters and gives a clear purpose, and an output schema exists to describe return values. However, the lack of annotations and absence of any usage context or behavioral notes leaves some gaps about response structure and edge cases, making it minimally complete but not rich.

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%, so the description is the primary source of parameter meaning. It explains latlng format, range units, and pagination semantics, adding significant value beyond the schema's titles and defaults.

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 clearly states 'Get Prague city district information' with a specific verb and resource. It is easily distinguished from sibling tools like get_bicycle_counters or get_parking_lots, which target different data types.

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 description implies usage through parameters like latlng and range, but does not explicitly state when to use this tool versus alternatives. No explicit context or alternative references are provided, though the intended use case is reasonably clear from the coordinates and radius parameters.

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