get_drug_targets

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

No annotations are provided, so the description must convey behavioral traits. It states the tool returns drugs in development and approved drugs, indicating it is a read-only query. However, it does not mention any potential side effects, permissions, or limitations such as rate limits or data freshness. The description is adequate but not comprehensive.

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 two sentences long, front-loaded with the verb 'Get', and contains no unnecessary words. It efficiently communicates the tool's purpose.

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 simplicity of the tool (one parameter) and no output schema, the description is mostly complete. However, it does not specify the format of the output (e.g., list of drugs with statuses, IDs, or links), which would help an agent parse results. Sibling tools are numerous, but the description provides enough context for selection.

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% for the single parameter 'gene', with a clear example. The description adds 'from Open Targets' but does not provide additional semantics beyond what the schema already conveys. Baseline 3 is appropriate.

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 retrieves drug target information from Open Targets for a given gene, specifically showing drugs in development and approved drugs. It uses a specific verb-resource combination and distinguishes from siblings like 'get_drug_gene_interactions' by focusing on drug targets rather than interactions.

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 the tool is used for getting drug targets for a gene, but provides no explicit guidance on when to use it versus alternatives such as 'get_drug_gene_interactions' or 'search_open_targets'. No exclusions or prerequisites are mentioned.

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