List MyChart Test Results

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds valuable context: automatic expansion of lazy-loaded lists, result ordering, the need for an authenticated session, and error handling behavior. No contradiction with annotations.

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 well-structured with a clear lead sentence, a compact return schema, and an error-handling section. Every sentence adds value and there is no redundancy or 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?

The description covers the full context: what the tool does, how it behaves (auto-expand, ordering), what it returns (detailed JSON schema), prerequisites (login), and failure paths (screenshot fallback). Given the tool's moderate complexity, this is complete.

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?

There are zero parameters (input schema is empty), so the baseline is 4. The description doesn't need to add parameter meaning because there are none; it wisely focuses on the return schema and behavior instead.

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 uses a specific verb ('Fetch') and resource ('full list of test results from the MyChart portal'), clearly distinguishing it from siblings like mychart_get_test_result and mychart_download_test_result. It also specifies content types (labs, imaging, pathology) and ordering.

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 states the prerequisite of a logged-in session and instructs to run mychart_login if not logged in. Also provides a fallback to mychart_screenshot if no results are recognized, effectively guiding when to use this tool versus alternatives.

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