lc_preview_add_case_entity

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. The term 'Preview' hints at a dry-run or simulation nature, but no details are given about side effects, output format, or whether any state changes occur. This lack of transparency is a significant gap for a tool that could involve mutations.

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 extremely concise (one short sentence), which aligns with conciseness, but it lacks structure. A single sentence fails to front-load key details or separate purpose from usage. While brevity is valued, it comes at the cost of completeness and clarity.

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's complexity (7 parameters, no output schema, no annotations), the description is severely incomplete. It does not cover the meaning of 'preview', expected output, parameter roles, or any behavior beyond the vague action. This inadequacy hinders correct agent invocation.

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 does not explain any of the 7 parameters (oid, case_number, entity_type, entity_value, note, verdict, token_ttl_seconds). The agent receives no guidance on parameter meaning, valid values, or constraints, forcing reliance solely on parameter names which may be ambiguous.

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 states the action ('Preview adding') and resource ('entity/IOC to a case'), providing clear verb+resource identification. However, it does not differentiate from sibling tools like lc_preview_add_case_artifact or lc_preview_add_case_detection, which have similar structures. The purpose is clear but lacks specificity for distinguishing between similar 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 usage guidelines are provided. The description does not specify when to use this tool versus alternatives, nor does it mention any prerequisites or conditions. With many sibling preview tools, the absence of usage guidance leaves the agent without direction for selection.

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