find_patients

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

No annotations provided, so description must cover behavioral traits. It mentions returning matching records but lacks details on matching logic (exact/partial), pagination behavior of 'limit', and what fields are returned beyond PatNum. Output schema exists but description does not leverage it.

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?

Two sentences, no fluff. Front-loads the core action and purpose, then adds usage guidance without extra verbiage.

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 search tool with 6 parameters and output schema, the description covers the essential purpose and workflow. However, it could improve by noting result limit behavior and result scope (basic info), but overall it is sufficient for an agent to use it correctly in conjunction with the schema and siblings.

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 0%. Description lists criteria types (name/phone/email/DOB) which map to parameters but does not explain 'limit' or clarify optionality (except that at least one is required). No format guidance for phone, birthdate, or email.

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 searches for patients by name/phone/email/DOB and returns matching records. It distinguishes from sibling tools like get_patient (which retrieves by ID) by specifying the workflow to find PatNum before using other tools.

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 states 'at least one criterion must be provided' and advises to use this tool to find a patient's PatNum before calling get_patient or other record-specific tools, providing clear when-to-use context.

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