search_patient

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

No annotations provided, so description carries full burden. It only states 'returns matching patient records with basic information', but does not disclose any behavioral traits such as read-only nature, authentication needs, pagination behavior, or rate limits. This is insufficient for a search tool.

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?

Description is extremely concise with three sentences: purpose, use-case, and examples. No fluff. Front-loaded with the most important information. Every sentence earns its place.

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?

Tool returns 'matching patient records with basic information', but no output schema is provided and description does not specify which fields are returned (e.g., name, ID, phone, status). With no output schema, description should clarify return structure. Also, parameters are well-documented in schema, but behavioral context is lacking.

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 coverage is 100%, so baseline is 3. The description adds examples of query values ('Eleanor Thompson', 'PT-10001', '555-0101') which provide practical context, but does not add new semantic meaning beyond what the schema already provides. Minimal additional value.

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?

Description clearly states the verb 'Search for a patient', the resource 'patient in the PointCare EMR system', and the search criteria 'by name, ID, or phone number'. It distinguishes from sibling tools like create_visit_note and get_patient_history by specifying the return of 'basic information' and use case before creating notes or retrieving history.

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 recommends usage 'before creating visit notes or retrieving history', providing context. While it doesn't explicitly list alternatives or when not to use, the context is clear enough for an AI to decide.

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