lc_preview_set_saved_query

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

The description says 'Preview' but doesn't explicitly state that no persistent changes are made. With no annotations, the agent must guess if this is a dry run. It also doesn't describe what the preview returns (e.g., validation errors, match counts). Minimal behavioral disclosure.

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 concise (single sentence) but too terse. It lacks structure (e.g., listing key parameters or behavior). It could be improved with a brief addition about the preview's purpose without sacrificing conciseness.

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 has 9 parameters, no output schema, and no annotations, the description is highly incomplete. It doesn't explain the preview's outcome or how parameters are used. Agents cannot reliably use this tool based solely on the description.

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 provides no parameter explanations. The 9 parameters (oid, name, query, etc.) are left completely undefined. The description adds zero value beyond parameter names.

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 verb 'Preview' and the resource 'saved LCQL query' with actions creating or updating. It differentiates from siblings like get/execute/delete by being a preview. However, it doesn't explicitly say 'simulate without saving' which would strengthen clarity.

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. It doesn't mention 'use this to validate before executing' or contrast with lc_execute_saved_query or lc_get_saved_query. Agents are left to infer usage.

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