BioMCP

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

With no annotations provided, the description carries the full burden. It discloses the requirement for an NCI API key and provides the source URL, which is valuable behavioral context. However, it lacks information about rate limits, error handling, authentication needs beyond the API key, or what happens if the organization_id is invalid. The description doesn't contradict any annotations since none exist.

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. It starts with a clear purpose statement, provides a bulleted list of retrieved details for quick scanning, includes important behavioral information (API key requirement), and ends with concrete example use cases. Every sentence adds value without redundancy.

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 that there is an output schema (which means the description doesn't need to explain return values), no annotations, and 100% schema coverage, the description provides good contextual completeness. It covers the purpose, usage examples, and key behavioral requirement (API key). The main gap is the lack of explicit guidance on when to use this versus the sibling 'nci_organization_searcher' tool.

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 fully documents both parameters (api_key and organization_id). The description does not add any parameter-specific information beyond what's in the schema, such as format examples for organization_id beyond what's already in the schema description. The baseline of 3 is appropriate when the schema does all the parameter documentation.

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 verb ('Get detailed information', 'Retrieves comprehensive details') and resource ('about a specific organization from NCI'), with specific examples of what information is retrieved. It distinguishes from the sibling 'nci_organization_searcher' by focusing on retrieving details for a specific organization rather than searching.

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 clear context for when to use this tool through example use cases ('Get details about a specific cancer center', 'Find contact information for trial sponsors', 'View organization's trial portfolio'). However, it does not explicitly state when NOT to use it or mention alternatives like the sibling 'nci_organization_searcher' for broader searches.

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