get_drug_similar_entities

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

The readOnlyHint annotation already signals a safe read operation, lowering the bar for additional disclosure. The description adds that similarity is based on PubMed embeddings, providing some behavioral context, but does not mention result limits, threshold interpretation, or how the embeddings are used beyond that.

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 entire description is a single sentence, highly concise and front-loaded. Every word is meaningful and directly communicates the core function without unnecessary detail.

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?

With five parameters, a required chembl_id, and an output schema, the description is far too brief. It lacks any explanation of how parameters like size or threshold affect results, what entity_names means, or what the output represents beyond the schema's structure.

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. The agent must infer the meaning of chembl_id, size, threshold, entity_names, and additional_entity_ids solely from their names and schema defaults, which is inadequate for correct invocation.

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 specific verb 'Find' and resource 'semantically similar drugs', with a clear method 'PubMed embeddings'. It distinguishes this tool from sibling tools like get_disease_similar_entities or get_similar_targets by explicitly focusing on drugs.

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 guidance is provided on when to use this tool versus other drug-related tools such as get_drug_info or get_drug_adverse_events. It does not mention alternatives, exclusions, or prerequisites.

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