Map Disease Drug Landscape

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

Annotations already declare readOnly/openWorld/idempotent, so the safety profile is covered. The description does add value beyond them by disclosing the underlying sources (Open Targets, ChEMBL, MONDO hierarchy) and calling the result 'bounded' and 'source-attributed', but it never explains what 'bounded' actually constrains, how expensive/long-running the multi-source aggregation is, or what happens when a disease has no approved drugs or targets.

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 title and first paragraph are well front-loaded with the verb, resource, and scope. However, the final sentence about business development and R&D portfolio decisions is marketing padding that adds nothing an agent can act on, and the output list is split awkwardly between the first and second 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?

An output schema exists, so return values need not be described, and the tool's read-only, idempotent nature is annotated. What remains thin is operational: no indication of aggregation cost, partial-failure behavior across three external sources, or expected result size for a broad disease – gaps that matter for an openWorld composite tool but are not fatal.

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?

Coverage is reported as 0%, so the description is the only prose channel, and it only says 'for a given MONDO disease' – it does not restate the MONDO:\d{7} format, note that the single required param is mandatory, or warn that non-MONDO identifiers will fail. The schema's regex pattern does most of the work here, keeping this at a minimum-viable 3 rather than lower.

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 ('Map ... therapeutic landscape for a disease') and enumerates concrete outputs: approved drugs, pipeline agents, druggable targets, and a summary. It implicitly separates itself from lookup-style siblings, but never names the neighbors an agent might confuse it with (get_disease_targets, find_drug_repurposing_candidates, compare_disease_target_overlap).

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 closing sentence ('used in business development, competitive intelligence, and R&D portfolio decisions') hints at the intended context but is audience framing, not invocation guidance. There is no explicit when-to-use / when-not-to-use, and no criterion distinguishing this composite landscape tool from the narrower sibling tools that return subsets of the same data.

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