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

With no annotations, the description carries the full burden and does well: it discloses that the calendar event stays, that the action is irreversible ('No undo'), and that user approval is required. It omits authorization details and what a successful response looks like, but the core behavioral impact is clear.

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?

Four short sentences, each adding distinct information. The key constraint (agent does not join, event stays) is front-loaded, followed by eligibility, irreversibility, and the required preview/approval step.

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 simple one-parameter mutation tool with no annotations and no output schema, the description covers behavior, preconditions, and irreversibility well. However, it leaves the agent without guidance on sourcing the required 'meeting_id', which is a notable gap given the empty schema description.

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 schema has 0% description coverage for the single parameter 'meeting_id', and the description does not explain where to obtain it, what format it takes, or how it relates to tools like 'list_meetings'. The parameter name is self-descriptive, but the description adds essentially no semantic guidance.

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?

States a specific verb and resource ('cancel_meeting'), and clarifies the exact effect: the agent will not join, but the calendar event remains. This distinguishes it from deleting a calendar event, though it does not explicitly compare against the nearby 'remove_agent_from_meeting' sibling.

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?

Gives clear preconditions: only scheduled meetings that have not started, and only after 'preview_cancel_meeting' and user approval. It says when not to use it (started or unscheduled meetings) but does not name alternative tools for adjacent scenarios.

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