calendars_get_appointment_notes

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is known. However, the description adds no behavioral context such as pagination behavior, sorting, or the fact that it returns a list. With annotations present, the description should add extra context, but it does not, so it only meets the baseline expected of annotations alone.

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?

While the description is extremely short, it is under-specified rather than concise. It lacks a complete sentence and provides no structure to guide an agent. The brevity is not a virtue because it omits essential details, resulting in a poor trade-off between length and utility.

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?

The tool requires appointmentId, limit, and offset, yet the description does not explain that notes are tied to a specific appointment, that pagination is necessary, or what the return type is. With no output schema, the description should clarify these aspects, but it does not. The description is incomplete for an agent to know how to use the tool correctly.

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%: limit, offset, and appointmentId are each described in the schema. The tool description adds no additional meaning beyond these, but since the schema is complete, the baseline is a 3. The description does not contradict or mislead, but it also does not enhance the parameter descriptions.

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 'Get Notes' is barely more than the tool name. It lacks the context that these are appointment notes and doesn't specify for which appointment or how they are retrieved. It does not distinguish from any other 'get' tool and is essentially a tautology, adding no new information.

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?

There is no indication of when to use this tool versus alternatives. No context about prerequisites, pagination, or the need for an appointment ID is provided. The description offers zero guidance on when this tool is appropriate.

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