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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds substantial context beyond them: login is required, a preview-by-default two-step confirmation with a previewHash is mandatory, and the effect is irreversible — the same conversation cannot re-apply or be recovered via re-confirmation or reopening follow-up. That is meaningful behavioral disclosure for a mutation tool.

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?

Front-loaded with the login precondition, then role rules, then the preview workflow and irreversibility. Arrow notation makes the flow scannable. It is dense but every clause carries information; no filler sentences.

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 destructive, non-idempotent mutation with no output schema and 0% schema coverage, the description supplies the preconditions, the confirmation flow, the parameter coupling, and the terminal consequences. It leaves only minor gaps (conversationId semantics, exact preview response shape), which is adequate-to-strong given the annotations.

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%, so the description must carry the load. It explains requestId (the current request to target), the status enum by role (CANCELLED vs DECLINED), and the preview/previewHash coupling (default preview; preview=false must be paired with the hash). This compensates well for most of the 5 undocumented parameters, though conversationId and previewHash format are only lightly implied.

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 description names a specific action pair (cancel/decline) on a specific resource (quick contact request) and clarifies the two role-dependent outcomes: initiator can only CANCELLED, recipient only DECLINED. This makes the action unmistakable and differentiates it from create_quick_contact_request and get_quick_contact_context. It does not explicitly name a sibling alternative, so 4 rather than 5.

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 states the login requirement and who may perform which status transition, and lays out the two-step preview workflow, which implies usage. However, it never says when to prefer this tool over alternatives or any exclusions beyond the state check. Guidance is present but implied rather than explicit routing.

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