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

Annotations already provide readOnlyHint=true, and the description redundantly states 'Read-only.' It adds the GraphQL query detail, which offers minimal extra context. No additional behavioral traits like error handling or auth requirements are disclosed, but the tool is simple enough that the description plus annotations suffice.

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 short sentences, front-loaded with the core action and resource. Every word earns its place, and there is no waste or redundancy beyond the harmless repetition of 'Read-only.'

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 single read-only tool with one fully described parameter and a readOnlyHint annotation, the description is complete. It clearly states what to provide (id) and that the operation is read-only, and no output schema is needed to understand the return value.

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?

The input schema covers the sole 'id' parameter fully with a description. The tool description does not add semantic meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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 states 'Fetch a single appointment by id,' which is a specific verb and resource with clear scope. It distinguishes from siblings like healthie_list_appointments by emphasizing single record retrieval.

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 clearly indicates when to use the tool: when you need one appointment by id. It doesn't explicitly mention alternatives or exclusions, but the context is clear and sufficient for a simple get-by-id operation.

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