Assess Target Druggability

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds valuable context: it integrates four signals, does not add scientific judgement, and is not a validated predictive model. This goes beyond annotations and clarifies behavioral traits.

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 with bullet points and clear sections. It is concise but includes necessary details about the four signals and their sources. No redundant sentences.

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 tool's complexity (integrating multiple signals) and the presence of an output schema, the description adequately covers what the tool does and its limitations. It could mention expected output format or compare to sibling tools, but it is mostly complete.

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%, so the description must provide parameter explanations. The description mentions signals that involve drugs and clinical compounds, which relates to include_clinical_stage, but it does not explicitly describe the parameters or their usage. Neither uniprot_id nor include_clinical_stage are explained.

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 that the tool provides a comprehensive druggability assessment for a protein target, outputting a HOT/WARM/COLD/NOT_DRUGGABLE classification. It details the four integrated signals, distinguishing it from sibling tools that focus on individual aspects like structural confidence or disease targets.

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 explains what the tool does but does not explicitly state when to use it versus alternatives. It mentions that it assembles existing public-database evidence and does not add scientific judgement, implying it is for simple evidence gathering rather than deep analysis, but this is not explicit.

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