update_appointment_notes

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

The description says 'add/replace' but does not clarify the exact behavior (e.g., does it always replace existing notes? Only add if none exists?). With no annotations, the description should disclose mutation behavior and prerequisites, but it does not.

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 very brief (one sentence) but lacks critical details. It is not concise in a helpful way—brevity here sacrifices completeness.

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 no output schema and no annotations, the description should thoroughly explain behavior and parameters. It fails to do so, leaving the agent uninformed about return values or side effects.

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 has 0% description coverage, and the description offers no explanation for the two parameters (appointment_id, note) beyond their names. An AI agent cannot infer what format the note should be in or how appointment_id is used.

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 action ('add/replace') and the target resource ('host-side note on appointment'), and it distinguishes itself from sibling tools like cancel_appointment or reschedule_appointment by focusing specifically on the note field.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., whether to use it for initial note addition vs. replacement, or what prerequisites exist). The description lacks any context for when to choose this tool.

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