lc_preview_delete_reliable_task

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

The description indicates a preview action (no actual cancellation) but does not disclose any additional behavioral traits like side effects, required permissions, or what 'preview' entails. With no annotations, the description carries full burden but provides minimal information.

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?

The description is very concise at one sentence with no fluff. However, it may be overly brief given the complexity of the tool.

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?

The description lacks essential context: no explanation of input parameters, no output schema details, and no mention of behavior beyond 'preview cancelling'. The tool is incomplete for effective use.

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?

No parameter descriptions are provided in the description or schema (0% coverage). The agent cannot determine the meaning or purpose of oid, task_id, selector, sensor_id, or token_ttl_seconds from the given text.

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 that the tool previews the cancellation of a pending reliable task. It uses a specific verb and resource, distinguishing it from actual deletion tools.

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?

No guidance on when to use this tool versus alternatives, such as the actual delete action or other preview tools. The description lacks context for appropriate use.

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