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

Beyond the destructive and non-read-only annotations, it discloses permanence, the inability to restore or reschedule the installation's single check-in, and the lack of impact on the installation report. It also explains behavior for sent or in-progress emails, including the cancelled:false result and accompanying status.

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 front-load the operation and then cover scope, irreversibility, and the important non-cancellable case. Every sentence adds operationally useful information, with no filler or repetition.

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 destructive mutation, the description covers nearly all essential preconditions and consequences, including an edge-case response. Its remaining gaps are followupId provenance and, because there is no output schema, incomplete documentation of successful results and other possible errors or already-cancelled behavior.

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 provides only the name followupId and its UUID format, with no parameter description. The description supplies general ownership and resource context but never explicitly maps the ID to the pending follow-up or explains where to obtain it, such as from schedule_installation_followup.

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 opening sentence gives a specific action, resource, owner, and state: permanently cancel the connected user's pending installation check-in email. It also distinguishes this operation from report withdrawal by stating that the installation report remains unchanged, and from scheduling by emphasizing that the check-in cannot be scheduled again.

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?

It explicitly limits use to the connected user's explicit request and to a pending check-in. The final sentence supplies a clear when-not boundary: emails already sent or being sent cannot be recalled, with the expected unsuccessful result described.

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