lc_preview_set_artifact_rule

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

The term 'Preview' implies a dry-run, but the description does not explain what the preview entails (e.g., validation, side effects, or response format). Without annotations, the behavioral traits are 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?

While very concise, the single sentence is insufficient for a tool with 8 parameters. It sacrifices necessary detail for 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 the lack of annotations, no output schema, and 8 parameters, the description is woefully incomplete. It does not explain the output or the distinction between creating and updating.

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 adds no meaning to the 8 parameters. The agent receives no help understanding 'oid', 'patterns', or other fields beyond their 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 that the tool previews creating or updating an artifact collection rule, which is specific and distinct from delete operations. However, it doesn't differentiate among multiple 'set_' 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 is provided on when to use this tool versus alternatives. The description lacks context about when a preview is necessary or how it compares to actual creation/update.

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