find_nearest_psw_for_client

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

The description adds context by specifying it ranks active PSWs and uses proximity to service address. However, with no annotations provided, it does not explicitly state read-only behavior, permissions, or side effects, and the phrase 'all active PSWs' is slightly ambiguous given the limit parameter.

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 two sentences, front-loaded with the purpose, and has no extraneous information.

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 tool has no output schema, so the description should clarify return values; it does not specify what is returned (e.g., PSW IDs, distances). Additionally, interactions with limit and max_distance_km are not described. However, the core behavior is clear enough for basic use.

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 three parameters have descriptions in the schema (100% coverage), and the description does not add any parameter-specific semantics. Baseline score of 3 applies.

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 the tool ranks active PSWs by proximity to the client's service address, using a specific verb (rank) and resource (active PSWs). It distinguishes from sibling tools by focusing on travel-efficient assignment for a single client.

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 provides a clear context ('Useful for finding the most travel-efficient PSW assignment') but does not explicitly mention alternatives or when not to use it. This gives clear context without exclusions.

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