cancel_meeting

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

No annotations provided; description only mentions cancellation and notification but omits critical behavioral details like permission requirements or side effects on related resources.

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?

Concise single-line purpose followed by structured Args/Returns; every sentence is informative with no redundancy.

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?

Covers key aspects given the tool's simplicity and the presence of an output schema, but could include context such as organizer requirements or cancellation limitations for full completeness.

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?

Description explains the purpose of each parameter (item_id as meeting identifier, message as optional cancellation note), adding value beyond the schema which only provides types and defaults.

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?

Clearly states the tool cancels/deletes a calendar meeting and notifies attendees, distinguishing it from sibling tools like update_meeting or respond_to_meeting.

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?

Implied usage is clear (use when you want to cancel a meeting), but lacks explicit guidance on prerequisites or when to avoid using it (e.g., not for accepting invitations).

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