lc_preview_spotcheck_run

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

No annotations provided, so description must disclose behavior. 'Preview' implies a dry-run or simulation, but it does not state whether actual execution occurs, what the output represents, or if any side effects exist. The description lacks critical behavioral details for a mutation-like tool.

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, concise but vague. It misses opportunity to front-load key details like what 'preview' entails. A bit too short to be useful, but not verbose.

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?

No output schema, no annotations, and 5 parameters with zero description coverage. The description fails to provide context about return values, prerequisites, or effects. Incomplete for a tool with this complexity.

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%, meaning no parameter descriptions. The tool description does not describe any of the 5 parameters (oid, tag, task, selector, token_ttl_seconds). The agent must infer meaning solely from parameter names and types, which is insufficient for correct usage.

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 previews running a fleet-wide spotcheck task, using a specific verb ('Preview running') and resource ('spotcheck task'). It distinguishes from sibling preview tools by specifying 'spotcheck', which is unique among the many lc_preview_* 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. With many sibling preview tools (e.g., lc_preview_sensor_task, lc_preview_reliable_task), it does not explain the specific scenario for using spotcheck over other preview actions.

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