get_target_depmap_essentiality

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

Annotations declare readOnlyHint=true, and the description's 'Fetch' is consistent with a read-only operation. However, the description adds no additional behavioral context beyond what the annotation already provides, such as data provenance, response size, or pagination behavior. It does not contradict the annotation.

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 with no unnecessary words. Every phrase ('DepMap', 'CRISPR essentiality scores', 'across cell lines') contributes directly to understanding what the tool does, achieving high clarity in minimal space.

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?

The tool has an output schema, so return values are likely documented there, and the read-only annotation covers safety. However, the description lacks parameter semantics and usage guidance, and there are no details about dataset versions or expected output format in the description. For a simple one-parameter tool with these structured fields, the description is adequate but leaves room for improvement.

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?

The schema describes only the parameter name 'ensembl_id' with no description (coverage 0%). The description does not clarify that this parameter specifies the target/gene for which essentiality scores are retrieved, nor does it indicate the expected format (e.g., Ensembl Gene ID). The meaning must be inferred from the tool name, which is a significant gap for a schema with zero parameter descriptions.

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 ('Fetch'), identifies the resource ('DepMap CRISPR essentiality scores'), and mentions the scope ('across cell lines'). This clearly distinguishes it from sibling tools like get_target_expression or get_target_info, which address different target-related data.

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 no guidance on when to use this tool over alternatives, no exclusion scenarios, and no mention of related tools. The intended context (e.g., 'when you need essentiality data for a target') must be inferred entirely from the tool name and description, which is insufficient for a tool with many siblings.

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