get_target_disease_biomarkers

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

Annotations declare readOnlyHint=true, which is consistent with 'Inspect' and covers the safety profile. The description adds no further behavioral details (e.g., pagination behavior, empty results, or data source nuances), but the output schema provides return structure. Given annotation coverage, a score of 3 is appropriate.

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 a single, clear sentence with no redundancy. It is front-loaded with the action and resource, making it highly concise and scannable.

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?

For a tool with 5 parameters and no parameter descriptions, the description is too sparse. It does not explain what counts as 'evidence,' how pagination works, or what fields can be requested. The output schema exists but the description still lacks essential usage context for effective invocation.

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 compensate for explaining parameters. It only implicitly references target and disease via the phrase 'target and disease,' but provides no details on size, cursor, or fields. The description adds minimal value beyond the schema itself.

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 action ('Inspect evidence for biomarker annotations') and a clear resource ('linking a target and disease'). It adequately differentiates from sibling tools like get_target_disease_evidence by focusing on biomarker annotations, though it could be even more explicit about the unique output.

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?

No guidance is provided on when to use this tool versus alternatives. The description implies use when interested in biomarker annotations for a target-disease pair, but does not mention exclusions or competing tools such as get_target_disease_evidence.

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