lc_preview_delete_yara_rule

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

The description states 'Preview deleting' implying a non-destructive dry-run, but it does not explain what the preview returns (e.g., summary of affected entities). With no annotations, the description should disclose behavioral traits like whether it is read-only or requires specific permissions.

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 at one sentence, but it lacks essential details about parameters and behavior. It is front-loaded but too minimal to be fully effective.

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 output schema, no annotation, and zero parameter descriptions, the description is incomplete. It does not explain the preview output, parameter semantics, or how this tool fits into the workflow of managing YARA rules.

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?

The input schema has three parameters (oid, name, token_ttl_seconds) with no descriptions in the schema (0% coverage). The description adds no explanation of these parameters, leaving the agent without guidance on what values to provide.

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 'Preview deleting a YARA scanning rule' clearly identifies the action (preview delete) and the resource (YARA scanning rule). It distinguishes from siblings like 'lc_preview_delete_yara_source' (deletes a YARA source) and 'lc_preview_set_yara_rule' (sets a rule).

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 such as 'lc_preview_delete_yara_source' or 'lc_preview_set_yara_rule'. There is no mention of prerequisites or context for using the preview delete action.

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