lc_cancel_action

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

No annotations exist, so the description carries the full burden. It discloses that the operation is local and does not involve server calls. However, it does not detail expected behavior on invalid tokens, idempotency, or side effects. Basic transparency is provided but not rich.

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?

Single sentence with no redundant words. The key information is front-loaded: 'Cancel one pending local action preview'. Efficient and clear.

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?

Given the tool's simplicity (one param, no output schema), the description covers the core action. However, it does not explain what a 'local action preview' is or that the token comes from a previous lc_preview_* call. Missing context that would help an agent correctly select and invoke the tool.

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 coverage is 0%, so the description must compensate. It implies that 'confirmation_token' identifies the preview to cancel, adding meaning beyond the raw schema. But it omits detail about the token's origin (e.g., from a preview creation call), which would improve usability.

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 clearly states the action 'cancel' and the resource 'pending local action preview'. It distinguishes from siblings like lc_confirm_action (which confirms) and lc_cancel_search_query (which cancels queries). The phrase 'without calling LimaCharlie' further differentiates this as a local-only cancellation.

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?

The description implies usage context: cancel a preview that has been created locally. It says 'without calling LimaCharlie', hinting it's for local previews. However, it does not explicitly state when to use this versus lc_confirm_action or other cancel tools, nor does it mention prerequisites like having created a preview first.

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