Medical Research MCP Suite

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'complete drug safety analysis' but doesn't specify what 'complete' entails, such as data sources, output format, limitations, or potential side effects like rate limits or authentication needs. This is inadequate 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 a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action and scope concisely, making it easy for an agent to parse quickly.

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 complexity of drug safety analysis, no annotations, no output schema, and low schema coverage, the description is insufficient. It doesn't explain what the analysis returns, how results are structured, or any behavioral traits, leaving significant gaps for an agent to invoke the tool correctly.

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 low at 25%, with only 'drugName' documented. The description adds context by implying parameters like 'includeTrials' and 'includeFDA' through 'across clinical trials and FDA reports', and 'timeframe' through 'analysis', but doesn't detail their semantics or defaults. This partially compensates but leaves gaps, aligning with the baseline for moderate 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?

The description clearly states the action ('complete drug safety analysis') and scope ('across clinical trials and FDA reports'), which is specific and distinguishes it from siblings like 'fda_adverse_events' or 'research_safety_details'. However, it doesn't explicitly differentiate from 'research_comprehensive_analysis' or 'research_safety_details', which might overlap in purpose.

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 guidance on when to use this tool versus alternatives like 'research_safety_details' or 'research_comprehensive_analysis' is provided. The description implies usage for safety analysis but lacks context on prerequisites, exclusions, or comparisons to sibling tools, leaving the agent to infer based on tool names alone.

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