openemr-mcp

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

No annotations provided, so description carries full burden. While 'Retrieve' suggests read-only behavior, the description fails to disclose error handling (what happens if drug not found), data freshness/caching, rate limits, or whether the operation is idempotent. No behavioral traits beyond the implied read operation are documented.

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 efficient sentence with zero waste. Front-loaded with action verb ('Retrieve'), followed by resource and specific content types. Every phrase earns its place by clarifying scope.

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 lookup tool, mentioning the specific clinical sections retrieved. However, with no output schema provided, the description omits return format details, error scenarios, and data structure expectations. Minimum viable but notable gaps 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?

Input schema has 100% description coverage ('Generic or brand name of the drug'), providing complete parameter documentation. The description adds no additional parameter context, examples, or format constraints, thus earning the baseline score for high schema coverage.

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?

Clear specific verb ('Retrieve') and resource ('FDA drug label') with precise content scope ('boxed warnings, contraindications, and indications'). However, it does not explicitly differentiate from siblings like openemr_fda_adverse_events or openemr_drug_interaction_check, requiring the agent to infer distinctions from the content types mentioned.

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?

No explicit when-to-use guidance or alternatives mentioned. The agent cannot easily determine whether to use this tool versus openemr_drug_interaction_check or openemr_fda_adverse_events without inferring from the specific label sections mentioned. No prerequisites or conditions are specified.

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