healthpoint_search_by_snomed

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

No annotations are present, so the description must fully disclose behavior. It only states 'Read-only', but omits details about authentication, rate limits, error handling, pagination behavior, or what happens when no results are found. This is insufficient for an AI agent to understand side effects or constraints.

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 extremely concise: two short sentences with no unnecessary words. It is front-loaded with the essential action and resource, making it easy to parse quickly.

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 outputs no schema and has three parameters, the description is minimally complete. It lacks details on the return format, result set size limits (beyond the schema-specified clamp), and how results relate to sibling tools. However, for a simple search tool, it meets basic needs.

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 covers 100% of parameters, so the description adds no extra meaning beyond what is already defined. The description mentions SNOMED CT codes but does not elaborate on format or usage beyond the 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 the action ('Search'), the resource ('Healthpoint HealthcareService records'), and the search criterion ('by SNOMED CT code'). It effectively distinguishes from siblings like healthpoint_search_services which likely performs broader searches.

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 mentions 'Read-only' which implies no destructive side effects, but it lacks explicit guidance on when to use this tool versus alternatives such as healthpoint_search_services. No prerequisites or context are provided.

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