lc_preview_delete_saved_query

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Preview deleting', which implies a non-destructive read-like operation, but it does not explicitly confirm idempotency, side effects, or what happens if the query does not exist. The meaning of 'preview' (e.g., returns a confirmation token or simply a dry-run result) is unclear.

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 a single sentence that concisely conveys the core action. It is appropriately sized for a simple tool, though adding a bit more detail would improve it without losing brevity.

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 three parameters and no output schema, the description is incomplete. It does not explain what the preview returns, how to interpret the result, or how the parameters identify the query. Users are left guessing about the tool's behavior and output.

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?

With 0% schema description coverage, the description should clarify parameters. It lists `oid` and `name` as required but does not explain their roles or why both are needed. The optional `token_ttl_seconds` is not mentioned. The description adds no value to parameter understanding.

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 tool does a 'preview deleting' of one saved LCQL query, which is a specific verb-resource combination. It distinguishes from sibling tools like `lc_delete_saved_query` (actual deletion) and `lc_list_saved_queries` by its preview nature, though it does not explicitly contrast with them.

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 gives no guidance on when to use this tool versus alternatives such as `lc_execute_saved_query` or `lc_get_saved_query`. There is no mention of prerequisites, when to preview versus actually delete, or what context the preview is useful for.

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