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

Annotations declare readOnlyHint=true, and the description repeats 'Read-only' and adds the GraphQL query shape. Since the annotation already covers the safety profile, the description adds minimal extra behavioral context beyond what the schema provides; it does not disclose pagination, response format, or rate limits.

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 concise, consisting of two short sentences that front-load the primary action and then list filter options. It includes the GraphQL syntax without unnecessary fluff, making it easy to scan and parse.

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 there is no output schema, the description explains the list purpose and filter options well. It does not mention return format or pagination, but for a filtered-list tool with read-only annotation, this is a minor gap. Overall, it provides enough context for an agent to understand the tool's role.

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 the baseline is 3. The description lists the GraphQL parameters and explains filters (patient, provider, date range, time-filter, status) but these mirror the schema descriptions without adding new semantic detail beyond parameter purposes.

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 lists appointments with optional filters by patient, provider, date range, time-filter, or status. It distinguishes itself from sibling tools like healthie_get_appointment (singular) and healthie_list_appointment_types by explicitly focusing on appointments and list behavior.

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 usage for listing appointments and mentions optional filters, but it does not explicitly state when to use this tool over alternatives or provide exclusionary guidance. The read-only nature and GraphQL query are context, but no direct comparison to siblings is given.

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