BioMCP

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

With no annotations provided, the description carries full burden. It discloses that the tool retrieves 'all linked publications' and lists specific types (results papers, background literature, etc.), which adds behavioral context. However, it doesn't mention whether this is a read-only operation, potential rate limits, authentication needs, or what happens when no publications exist for a given trial.

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 well-structured and appropriately sized. The first sentence clearly states the purpose, followed by a bulleted list of what's included, and ends with additional useful information about PubMed IDs. Every sentence earns its place with no wasted words.

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 an output schema (which handles return values), no annotations, and a simple single-parameter input schema with full coverage, the description provides good contextual completeness. It explains what types of publications are retrieved and includes the PubMed ID detail, which adds value beyond what structured fields provide. The main gap is lack of behavioral transparency about operational constraints.

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 already documents the single parameter. The description doesn't add specific parameter semantics beyond what's in the schema, but with only one parameter and high schema coverage, the baseline is appropriately high. The description does imply the parameter's purpose by stating the tool fetches publications 'for a clinical trial'.

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 with specific verb ('Fetch') and resource ('publications and references for a clinical trial'), and distinguishes it from siblings like 'trial_getter' or 'trial_searcher' by focusing specifically on publications and references rather than general trial information or search capabilities.

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 implies usage context (when you need publications for a clinical trial) but doesn't explicitly state when to use this tool versus alternatives like 'article_getter' or 'article_searcher'. No guidance is provided about when NOT to use this tool or about prerequisites beyond the required NCT ID parameter.

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