openemr_visit_prep

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

No annotations; description claims evidence-linking and no hallucination but does not disclose side effects, whether it modifies data, or if it's read-only.

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?

Single sentence with clear front-loading of purpose and key output components; effectively concise.

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?

Missing output format details (e.g., text vs. JSON); with no output schema, description should clarify what the brief looks like and any additional context needed.

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 covers both parameters fully; description adds no additional meaning beyond the schema, though it mentions output components not linked to parameters.

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 tool generates a pre-visit clinical brief listing top risks, medication safety, care gaps, and agenda. It differentiates from sibling tools which focus on specific data retrieval or actions.

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?

Implies use for pre-visit planning but lacks explicit when/when-not guidance or comparison to sibling tools like medication list or drug interaction check.

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