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

The readOnlyHint annotation already declares the safe-read profile, so 'Read-only' is largely redundant. It adds some value by exposing the underlying GraphQL query and its arguments, which hints at the supported filters and pagination, but says nothing about page size, result ordering, or volume of returns.

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 compact sentences, front-loaded with the core purpose then the filtering scope and the query mapping. No filler, though the third clause is mostly implementation detail an agent does not need to select the tool.

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?

No output schema exists, so the description is not obliged to explain return values, and the schema fully documents the filters. The only gap is pagination behavior: an offset is accepted but no page size or default result count is described, so an agent cannot predict how much data comes back.

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 100% and each of the three parameters is documented in the schema, so the baseline is 3. The description mirrors the same argument names in the GraphQL signature without adding format, default, or semantics beyond what the schema already states; it also lists should_paginate, which is not an exposed parameter.

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 (completed form submissions) and disambiguates the domain jargon by equating submissions with 'charting notes / filled intake forms'. This implicitly separates it from the sibling healthie_list_forms (templates), but the distinction is left to inference rather than stated.

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?

'optionally scoped to a patient or a form template' tells the agent the two filtering modes, which is real usage guidance. However, no alternative tool is named (e.g. list_forms for templates) and no when-not condition is given, so guidance remains implied.

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