find_libraries_near_coordinates

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

With no annotations, the description carries full responsibility. It discloses sorting by distance, radius/limit bounds, and include_closed default. It also notes performance (skips geocoding). However, it omits edge-case behavior (e.g., no results) and any error conditions, preventing a top score.

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 purpose is stated in one sentence, usage guidance in one sentence, and parameters are listed in a clean, scannable format. Every word contributes; no redundancy.

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 simple lookup tool with no output schema, the description provides the core behavior and all parameter constraints. It does not specify the exact structure of returned branches, but this is a minor gap given the tool's simple purpose.

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?

All five parameters are explained with types, units (WGS84, miles), ranges (0.1–50, 1–100), and defaults. Given schema description coverage is 0%, this fully compensates and adds meaning beyond the bare schema.

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 it finds public library branches nearest to coordinates, sorted by distance. It distinguishes itself from sibling find_libraries_near_address by noting it skips geocoding and is faster, making the purpose unmistakable.

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?

Explicitly instructs to use this tool when coordinates already exist and directly compares to the alternative, providing clear when-to-use and why. This is a model example of usage guidance.

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