获取健康档案摘要

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

No annotations are provided, and the description does not disclose behavioral traits such as permissions needed, side effects, or whether it's a read-only operation. It only describes the returned data, lacking transparency for a tool with no annotation support.

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 sentence that efficiently conveys the tool's purpose and content. It is front-loaded and contains no unnecessary words, though it could be slightly more structured (e.g., bullet points) for clarity.

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?

Given no output schema and no annotations, the description covers the main return items but does not specify the format or any prerequisites (e.g., patient selection). It is adequate for a simple read tool but lacks completeness for an agent to fully understand the response structure.

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?

The input schema has zero parameters, so schema coverage is 100% by default. The description adds meaning by stating it returns a summary for a 'single patient,' which implies patient context must be set elsewhere. With 0 params, a score of 4 is appropriate as the description provides useful context beyond 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?

The description clearly states the tool returns a health summary for a single patient, listing specific components (current medications, allergies, conflict alerts, dietary restrictions, treatments, timeline, and related reports). This differentiates it from siblings like health_profile_get or health_medication_list.

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?

The description implies the tool is for retrieving a comprehensive summary, but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives. Usage is implied but not fully clarified.

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