get_patient_vital_signs

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

No annotations provided; description only indicates it returns a dictionary with vital signs. Omits behavioral aspects like error handling, empty results, or any side effects.

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?

Concise and structured with clear sections for args and returns. No extraneous text.

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?

Covers parameters and return type, but lacks details on pagination, result ordering, or how vital signs differ from general observations, especially given many siblings.

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?

With 0% schema description coverage, the description adds meaningful context: explains patient_id as FHIR ID and date format as YYYY-MM-DD or range, which is not in the schema.

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 verb (retrieve), resource (vital signs observations), and scope (a specific patient). Distinguishes from siblings like get_patient_observations (broader) and get_observation_by_id (single observation).

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?

Provides parameter descriptions but no explicit guidance on when to use this tool over alternatives, such as differentiating from other patient-specific retrieval tools.

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