calendars_update_appointment_note

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds no behavioral context beyond what annotations already imply. It does not state what the update does, whether it overwrites the entire note body, or any side effects. It neither contradicts annotations nor provides meaningful extra information.

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?

At two words, the description is severely under-specified rather than concise. It lacks any structure, front-loading, or explanatory value. Every word is wasted because it adds nothing beyond the tool name.

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 tool with four parameters and no output schema, the description is highly incomplete. It does not mention that it updates the body of a note associated with an appointment, nor does it explain the relationship between appointmentId, noteId, and body. The description provides nearly no contextual information needed for correct invocation.

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 75% (three of four parameters have descriptions). The description does not illuminate any parameter meaning; it only says 'Update Note'. For the undocumented 'userId' parameter, no clarification is given, and the description does not compensate for the moderate coverage gap.

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 'Update Note' is essentially a tautology of the tool name, restating the verb and noun without specifying that this is about appointment notes. It fails to distinguish this tool from other note-update tools (e.g., contacts_update_note) and provides no context about the resource type.

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 guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, typical scenarios, or exclusions. An agent cannot determine when this should be selected over similar calendar note tools.

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