calendars_delete_appointment_note

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

The description adds no behavioral context beyond what annotations already provide. Annotations indicate destructiveHint=true and readOnlyHint=false, but the description does not mention consequences, permissions, or any additional side effects. No added value.

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 extremely terse ('Delete Note'), which is not conciseness but under-specification. It lacks any structural elements like front-loaded context or clarifying phrases. It does not effectively serve its purpose.

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 2-parameter destructive operation, the description should clarify what the tool acts on and any relevant context. It fails to mention that it's an appointment note, nor does it reference the parent appointment. The annotations cover destructive behavior, but the description is too thin to be complete.

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 100%, so both appointmentId and noteId are documented in the schema. The description adds no additional meaning, but the baseline of 3 applies because the schema carries the full semantic load.

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 'Delete Note' provides a verb and a generic resource, but lacks specificity about what note (appointment note) is being deleted. It does not distinguish from other delete tools in the same domain, such as calendars_delete_calendar_resource or calendars_delete_event. The name itself adds context, but the description does not clarify the scope.

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. No mention of prerequisites, context, or conditions under which it should be selected over similar delete tools. Completely absent.

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