mymedi-ai-mcp-server

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

No annotations are provided, so the description carries full burden. It mentions the data source (OpenFDA) and return content (drug details, indications, interactions, AI analysis), but lacks critical behavioral details: whether this is a read-only operation, rate limits, authentication needs, error handling, or what 'AI analysis' entails. For a tool with external API calls and no annotations, this is inadequate.

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?

The description is a single, efficient sentence that front-loads key information: action, source, and returns. There's no wasted text, though it could be slightly more structured (e.g., separating source from outputs). Every word 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?

Given no annotations, no output schema, and an external API tool with potential complexity, the description is incomplete. It doesn't cover behavioral traits (rate limits, auth), output format details, or error scenarios. The mention of 'AI analysis' is vague without explanation. For this context, more completeness is 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 description coverage is 100%, so the schema fully documents both parameters (drugName with format, searchField with enum). The description adds no parameter-specific information beyond what's in the schema—it doesn't explain how parameters affect the enrichment process or provide examples. Baseline 3 is appropriate when schema does all the work.

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 the tool's purpose: 'Drug information enrichment via OpenFDA' specifies the action (enrichment) and resource (drug information). It distinguishes from siblings by focusing on drug data rather than claims, codes, compliance, etc. However, it doesn't explicitly differentiate from similar enrichment tools like provider_enrich beyond the drug focus.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, constraints, or comparison to sibling tools like provider_enrich or code_lookup. The agent must infer usage from the purpose alone without explicit when/when-not instructions.

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