mymedi-ai-mcp-server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'AI-enriched' and the types of data returned (practice details, specialties, affiliations, market context), but doesn't cover important aspects like whether this is a read-only operation, potential rate limits, authentication requirements, data freshness, or error conditions. The description is insufficient for a tool with no annotation coverage.

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 appropriately concise - two sentences that directly state the tool's function and what it returns. It's front-loaded with the core purpose. While efficient, it could be slightly more structured by separating purpose from return details.

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 the tool has no annotations and no output schema, the description should do more to compensate. It mentions what data is returned but doesn't describe the format, structure, or completeness of the response. For a single-parameter tool with 100% schema coverage but no output schema, the description is minimally adequate but leaves important gaps about the return value.

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% (the single parameter 'npi' has a clear description: '10-digit NPI number'). The description adds no additional parameter information beyond what the schema provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in description.

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: 'AI-enriched provider intelligence from NPI number' specifies the action (enriching) and resource (provider intelligence). It distinguishes from siblings like provider_search (searching) and drug_enrich (different resource). However, it doesn't explicitly contrast with all siblings like market_analysis or ner_extract.

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 when to choose provider_enrich over provider_search, or how it differs from other enrichment tools like drug_enrich. There's no context about prerequisites, typical use cases, or exclusions.

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