lc_preview_delete_group

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

Annotations are absent, so the description must carry behavioral disclosure. The word 'Preview' implies a dry run, but the description does not confirm that no changes occur, what the output contains, or any side effects. Minimal transparency beyond the action type.

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 short (one sentence) and front-loaded with purpose. However, it is too terse to be effective; every sentence should earn its place, but this one fails to provide necessary detail.

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?

The tool has low complexity (2 params, no output schema), but the description does not explain what 'preview' entails, what the output will be, or how to interpret results. For a preview action, the expected output is critical context, and its absence makes the description incomplete.

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 two parameters. 'group_id' and 'token_ttl_seconds' are not explained. The description repeats the tool name without elaborating on what each parameter does or how to use them.

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 deleting an organization group. It uses a specific verb 'Preview deleting' and identifies the resource 'organization group'. It distinguishes from other preview tools by specifying 'group', but not from sibling tools like lc_delete_group (not listed) or other preview_delete_* 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. There is no mention of when to preview versus actually deleting, or comparison with other preview or delete tools. The agent is left to infer usage from the tool name alone.

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