get_disease_similar_entities

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

Annotations already declare readOnlyHint=true, so the description's addition of 'based on PubMed embeddings' provides useful methodological context beyond the annotation. It does not contradict annotations, and it clarifies that results are semantic similarities rather than exact matches, though it does not detail threshold or sorting behavior.

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, front-loaded sentence that conveys the core purpose without wasted words. Every element ('find', 'semantically similar', 'diseases', 'PubMed embeddings') adds value.

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?

An output schema exists, which partially covers return values, but the description lacks parameter semantics and usage alternatives. Given five parameters with no schema descriptions, the description is not rich enough to fully compensate for these gaps.

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 0%, and the description does not explain any of the five parameters. 'efo_id' is implied by the tool name, but 'threshold', 'entity_names', 'additional_entity_ids', and 'size' remain undocumented, leaving the agent to guess their meanings and relationships.

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 uses a specific verb 'find' and clearly identifies the resource 'diseases' plus the method 'based on PubMed embeddings'. It distinguishes this from sibling tools like get_drug_similar_entities and get_similar_targets by focusing on diseases and semantic similarity.

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 when semantically similar diseases are needed, but it does not explicitly state when to use this tool over alternatives or provide any exclusions. The disease-focused wording provides clear context, but no alternative guidance is given.

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