healthpoint_find_nearby_services

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

The description declares 'Read-only', which is a key behavioral trait, especially with no annotations provided. However, it does not disclose other behaviors like result ordering, pagination, or default radius, leaving some uncertainty for a tool with 6 parameters.

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 core purpose, and contains no filler. Every word serves a purpose.

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 has 6 parameters, no output schema, and no annotations, the description provides minimal context. It covers the basic intent but lacks details on return format, default behavior for radius, or how text search interacts with location, making it adequate but not thorough.

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 100%, so the schema already documents all parameters. The description adds no additional meaning beyond the schema, resulting in a baseline score of 3.

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 verb 'Find', the resource 'nearby Healthpoint HealthcareService records', and the method 'by latitude/longitude'. It distinguishes from sibling tools like healthpoint_get_service (single resource) and healthpoint_search_services (likely text-based).

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 for location-based proximity searches but provides no explicit guidance on when to use this tool versus alternatives such as healthpoint_search_services. No exclusion criteria or prerequisites are mentioned.

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