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

With no annotations, the description carries the full burden, and it does disclose the single most important trait: 'Nothing changes', i.e. this is non-mutating. It says nothing about what happens when meeting_id doesn't exist, permissions required, or the shape of the returned preview beyond 'which meeting'.

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?

Three terse sentences, front-loaded with the action, then the safety property, then the workflow instruction. No filler and nothing buried.

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 one-parameter preview tool with no output schema and no annotations, the description covers purpose, non-mutation, and user-facing sequencing — the essentials. It stops short on parameter sourcing and on what the preview actually contains, which matters since there is no output schema to fall back on.

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 description coverage is 0% and the description never mentions meeting_id — the only parameter. The agent can guess that a required string id selects the meeting, but nothing is added about expected format, source (list_meetings/get_meeting), or behavior for invalid ids.

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?

Names a specific action (show which meeting would be skipped) plus the scope, and the phrase 'Nothing changes' makes it identifiable as a dry-run counterpart to cancel_meeting. It doesn't name the sibling cancel_meeting explicitly, so the agent must infer the pairing from the shared 'meeting' + 'cancel' naming.

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?

'Call first and show the user' gives explicit sequencing guidance — this is a pre-flight step whose result must be surfaced to the user before the real action. The implied alternative (the actual cancellation) is never named, so the agent has to infer which tool to call next.

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