openemr-mcp

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

No annotations are provided, so the description carries the full burden. While 'Delete' implies destruction, the description fails to specify if this is permanent, irreversible, or has cascading effects on related records. It omits auth requirements or safety warnings appropriate for a healthcare context.

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?

Extremely efficient at 6 words with zero redundancy. Every word earns its place; the description is immediately scannable and front-loaded with the action.

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?

Adequate for a single-parameter delete operation with complete schema coverage, but gaps remain: no output schema exists and the description does not specify the return value (success boolean, deleted object, void) or confirm the operation's permanence given the lack of annotations.

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 the parameter flag_id is fully documented in the schema itself. The description adds minimal semantic value beyond the schema, only implying the parameter with 'by ID'. Baseline score applies.

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?

States a specific verb (Delete) and resource (drug safety flag) with scope (by ID). However, it essentially restates the tool name with minimal elaboration and does not explicitly differentiate from sibling tools like openemr_drug_safety_flag_update in the description text.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., when to delete vs. update a flag), nor does it mention prerequisites like obtaining the flag_id from openemr_drug_safety_flag_list first.

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