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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description earns credit by disclosing the shape of the result beyond annotations: highest phase reached FOR THAT CONDITION, the trial/label URL behind it, FDA UNII, and the related Inxight condition labels. It does not address pagination behavior or unknown-condition handling.

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 purpose is front-loaded in the first clause, and subsequent sentences each add distinct value (filtering hint, return fields, drill-down labels). It is dense and somewhat run-on, but almost nothing is wasted.

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?

With no output schema, the description carries the burden of describing returns and does so (phase, URL, UNII, related condition labels). Parameters are fully covered by the schema and safety is covered by annotations, leaving only minor gaps such as paging expectations and empty-result behavior.

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%, so the schema already documents limit, offset, condition, and the development_status enum. The description largely restates this (condition examples, 'Clinical' = investigational only), adding little syntax or semantics beyond what the schema carries. Baseline 3 applies.

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 states a specific verb+resource and the direction of the lookup: give a condition, get substances approved for or in development for it, from NCATS Inxight Drugs. That directionality implicitly contrasts with siblings like inxight_substance or inxight_search, but no sibling is actually named, so it falls short of a 5.

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?

It clearly frames when to use it ('give a disease or indication ... and get each substance') and gives a concrete narrowing rule ('Narrow with development_status "Clinical" to see only investigational drugs'). It does not name an alternative tool or state when NOT to use this one, so it stops short of explicit routing.

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