Cross-Disease Structural Target Overlap

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety is covered. The description adds the analytical shape (shared vs unique vs Jaccard), but with an output schema present this largely restates return structure rather than disclosing new behavior like computation method, limits, or provenance.

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?

Front-loads the verb+resource in the first sentence, then uses a clean 'Returns:' bullet list. The interposed 'a key analysis for drug repurposing...' clause leans slightly toward marketing but still conveys use context.

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 nested schema is well documented and an output schema exists, so the description need not enumerate return fields — yet it does, giving the agent a clear picture of shared/unique/Jaccard outputs. It is broadly complete for a read-only comparison tool.

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 description only refers to 'two diseases' and adds no meaning beyond the schema, which itself documents mondo_id_a (with example), mondo_id_b, and target_limit's 1–50 range. Parameter semantics are adequately covered by the nested schema descriptions, so a baseline 3 is warranted.

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?

States a specific verb and resource — 'Compare the protein target landscapes of two diseases' — and the sub-bullet clarifies the output construct ('shared and unique targets'). It doesn't explicitly differentiate from similar siblings such as get_common_disease_targets or compare_proteins_topologically, so an agent must infer the distinction.

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 phrase 'a key analysis for drug repurposing, identifying shared mechanisms, and understanding comorbidity' implies when the tool is valuable, but it offers no explicit when-not guidance and does not name the closely related sibling get_common_disease_targets as the alternative. Usage is implied rather than prescribed.

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