mah_list_past_visits

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

Annotations only declare readOnlyHint=true, so the description carries the rest: it discloses the compact output shape { items, complete, note } and the paging contract (complete=false signals older visits, note explains how to use before). That is meaningful behavior beyond the annotation, though it doesn't mention the view parameter's effect or any auth requirements.

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?

Two sentences, front-loaded with the core purpose, followed by the one piece of non-obvious behavior (output shape and paging). No 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?

Although there is no output schema, the description describes the return shape and pagination contract, which is the key missing context for this read-only list tool. What remains unstated—grouping structure details and auth prerequisites—is minor.

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 description coverage is 100%, so both parameters are already fully documented in the schema, setting the baseline at 3. The description reinforces the `before` paging semantics and the `complete`/`note` signals but adds no syntax or format detail 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?

"List past MyAtriumHealth visits, grouped by organization" gives a specific verb, resource, and grouping scope. It implicitly distinguishes itself from the sibling mah_list_upcoming_visits via "past", though it never names that sibling explicitly.

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 intended use (retrieving historical visits) is implied by "past" rather than stated, and there is no explicit when-to-use versus when-not guidance or named alternative. The pagination explanation is behavioral rather than usage guidance.

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