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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the tenant-ownership scope, the lifecycle precondition (not yet dispatched), and the requirement for explicit confirmation — none of which appear in the annotations.

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?

Two short sentences with zero filler, front-loading the action and then the precondition. Nothing could be removed without losing a constraint.

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?

An output schema exists, so return values need not be explained, and annotations carry the destructive/idempotent profile. The description supplies the missing lifecycle precondition; only minor gaps remain around the idempotency key's role.

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%, but the schema itself is unusually self-documenting (confirm is const true, meetingId and idempotencyKey carry regex patterns and length bounds). The description adds meaning only for `confirm` via 'Requires explicit confirmation', and says nothing about idempotencyKey or what a meetingId refers to.

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 ('Cancels a tenant-owned meeting agent') plus a scoping precondition ('that has not yet been dispatched'), which is far more precise than the name alone. It does not explicitly name schedule_meeting_capture as the inverse/mistake case, but the verb makes the distinction obvious.

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?

'has not yet been dispatched' is an explicit when-to-use boundary that tells the agent this is not the tool for already-running captures. However, no alternative tool is named for the dispatched case, leaving the agent to search siblings.

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