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

No annotations provided, but description fully discloses that results are partial/non-exhaustive, metadata is internal taxonomy not clinical verification, and pathway_tags are raw graph metadata. No contradictions.

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?

Description is clear but verbose with multiple caveats. Each sentence adds value, but it could be more concise by grouping related warnings.

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?

No output schema, so description must compensate. It mentions output fields (type labels, graph_status, etc.) but does not fully describe the response structure or return type completeness.

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 describes both parameters; description adds meaningful usage guidance (dose_value vs dose_mg) beyond schema. The high schema coverage (100%) raises baseline, but the extra info justifies above average.

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?

Clearly states the tool finds supplements affecting a biomarker, with specific exclusions. Distinguishes from siblings like get_biomarkers_for_supplement or get_interventions_for_biomarker.

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 lists excluded types and warns about metadata limitations. Provides parameter usage guidance (use dose_value/dose_unit). Lacks explicit when-not-to-use or direct alternatives.

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