lc_preview_remove_case_entity

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

With no annotations, the description must cover behavioral traits. It only hints at non-destructive nature ('preview') but doesn't confirm what the preview returns, whether it mutates state, or any constraints. No mention of authorization or side effects.

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?

Extremely concise (6 words), but this comes at the cost of missing essential details. It is front-loaded but lacks structure; a single sentence is not well-structured for complex tools.

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 4 parameters, no output schema, and many similar preview tools, the description is incomplete. It does not explain the return value, how the preview works, or differentiate from sibling previews.

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%, putting full burden on the description. The description does not explain any of the 4 parameters (oid, entity_id, case_number, token_ttl_seconds). Parameter names alone are insufficient to convey meaning.

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 action ('preview removing') and resource ('entity from a case'). It distinguishes from siblings like 'lc_preview_remove_case_artifact' or 'lc_preview_add_case_entity' by specifying the entity removal context.

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 its siblings (e.g., actual removal vs preview, or other preview removals). No context about typical scenarios or prerequisites.

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