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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions the tool returns 'ten closest pharmacies' and sorts by distance, it fails to describe critical behaviors such as response format, error handling, data freshness, rate limits, or authentication requirements. For a location-based query tool with zero annotation coverage, this leaves significant gaps.

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 a single, well-structured sentence that efficiently conveys the core functionality: action, resource, quantity, constraints, and sorting. Every word earns its place with no redundancy or fluff, making it easy to parse and front-loaded with essential 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?

Given the tool's moderate complexity (location-based query with filtering), lack of annotations, and no output schema, the description is minimally complete. It covers the basic purpose and parameter intent but omits details on output structure, error cases, and operational constraints. It meets the bare minimum for understanding what the tool does but not how it behaves fully.

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 input schema has 0% description coverage, so the description must compensate. It adds meaning by explaining that the 'address' parameter is used to calculate distance and filter results, which goes beyond the schema's bare 'Address' title. However, it doesn't specify address format requirements, validation rules, or handling of ambiguous inputs, leaving some semantic gaps.

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's purpose: 'Get ten closest pharmacies on duty today, sorted by distance to the given address.' It specifies the verb ('Get'), resource ('pharmacies'), and key constraints ('ten closest', 'on duty today', 'sorted by distance'). However, with no sibling tools mentioned, it cannot demonstrate differentiation from alternatives.

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 no explicit guidance on when to use this tool versus alternatives. It implies usage for finding nearby duty pharmacies but offers no information about prerequisites, limitations, or scenarios where other tools might be more appropriate. With no siblings listed, this is a missed opportunity for basic context.

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