lc_preview_delete_exfil_watch

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

No annotations are provided, so the description carries full burden. It says 'Preview deleting' but does not explicitly state that it is a dry run or what side effects occur. There is no mention of the output, return format, or any behavioral traits beyond the vague verb.

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 extremely brief (one sentence) but fails to convey necessary information. Conciseness should not come at the expense of clarity; here, the brevity makes the description inadequate for an AI agent to understand usage properly.

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 no output schema, no annotations, and 0% schema description coverage, the description is completely inadequate. It does not explain the purpose of the preview, the expected outcome, or how parameters relate to the operation. The tool definition leaves too much ambiguity.

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%, and the description does not add any meaning for the three parameters (oid, name, token_ttl_seconds). The parameter names are somewhat self-explanatory but lack context such as data types, formats, or examples, which is critical for correct invocation.

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 uses a specific verb ('Preview deleting') and resource ('exfil watch rule'), making it clear what the tool does. However, it does not clarify what 'Preview' means (e.g., dry run vs. actual deletion), and sibling tools like lc_preview_create_exfil_watch suggest a pattern but the distinction from a potential actual delete tool is not stated.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, expected inputs, or scenarios where this tool is appropriate. Sibling tools include many preview_delete_* tools but no explicit direction.

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