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

The readOnlyHint annotation already indicates read-only; the description redundantly says 'Read-only' but adds a GraphQL query signature. However, it does not disclose additional behavioral traits such as return format, pagination behavior, or rate limits. With annotations covering safety, the description adds marginal value, matching a 3.

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 two sentences long and front-loads the purpose. The GraphQL detail is somewhat technical and may be extraneous for typical users, but the text is efficient and free of fluff, earning a 4.

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?

For a simple list tool with three optional parameters and read-only annotation, the description covers purpose, filters, and read-only nature. Without an output schema, it doesn't describe return values, but this is acceptable for a basic list operation. Overall, it's sufficiently complete for the tool's complexity.

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% for all three parameters, so the schema fully documents each. The description restates scoping in prose and includes a GraphQL query with should_paginate, a parameter not present in the input schema, which may confuse users. Since the schema carries the burden, the description adds little beyond baseline.

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 'List completed form submissions (charting notes / filled intake forms)' with a specific verb and resource. It also mentions optional scoping to patient or form template, which distinguishes it from sibling tools like healthie_list_forms that likely deal with form templates, not submissions.

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 provides clear context: use this to list completed form submissions, optionally filtered by patient or template. It doesn't explicitly exclude alternatives, but the phrase 'completed form submissions' implicitly differentiates from healthie_list_forms (templates) and other list tools. No explicit when-not guidance, but the context is clear enough for a 4.

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