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 description's added value is that the data is human-reviewed, carries provenance and extractor versions, and may be incomplete via 'pending-review counts' - useful reliability context beyond the annotations. It stops short of noting auth needs, freshness/latency, or pagination.

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?

Two sentences, front-loaded with the core action and followed by the usage trigger. The middle payload list is dense with domain jargon, but each clause carries identifying information rather than filler.

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 a 1-parameter schema and an output schema present, the description need only convey purpose and usage, both of which it does. Minor gap: it doesn't indicate whether the returned signals can be empty or how pending-review counts should be interpreted, though that is largely a return-value concern covered by the output schema.

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?

Only one parameter, and the schema description coverage is 100%, so the schema already documents project_id fully (UUID of the project to query). The description adds nothing beyond what the schema provides, which is the baseline 3 for well-covered single-parameter schemas.

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+resource ('Fetch human-reviewed drug-specific clinical-risk signals for a project') and enumerates the payload's distinguishing contents (biomarker quality, Phase 1 ORR flag-only data, provenance, extractor versions, pending-review counts). An agent can tell this apart from siblings like get_evidence or get_methodology without opening either schema.

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?

Explicitly states when to use it: 'before interpreting model 2.6.0 drug-specific multipliers or flags.' That is a clear contextual trigger, but no when-not condition and no named alternative sibling are given.

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