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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description adds genuinely useful traits beyond them: default newest-first ordering and a hard 200-record cap. It omits what happens past 200 (truncation? error?) and whether the default date range is unbounded, which keeps it short of a 5.

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?

A single front-loaded sentence with the resource, scope, cap, and filters in descending order of importance; the parenthetical examples earn their place by disambiguating what a 'biomarker observation' is. Zero 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?

Adequate for a filtered-list tool whose annotations carry the safety profile and which has no output schema to explain. Remaining gaps are the unspecified 'order' parameter behavior and the consequence of exceeding the 200-record cap, both of which an agent would want before calling.

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 coverage is only 25% (only 'biomarker' is documented in-schema), so the description must compensate. It covers biomarker-name and date-range filtering conceptually, but never mentions the 'order' parameter or explains how to reverse the newest-first default, and adds no format detail beyond the schema's own date pattern.

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 ('List') and resource ('biomarker observations') with concrete examples (lab values, glucose, ketones, weight) and scope (newest first, up to 200, filterable). It does not explicitly differentiate itself from the sibling vora_get_latest_biomarkers, leaving the agent to infer that this is the full-history variant.

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?

Implies usage through 'filterable by biomarker name and/or date range' and the newest-first default, but never says when to prefer this over vora_get_latest_biomarkers or when filtering is required versus optional. No exclusions or prerequisites are stated.

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