lc_preview_delete_external_adapter

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

With no annotations, the description must disclose behavior fully. It implies a non-destructive preview but fails to state whether the action modifies state, requires permissions, or has side effects. The preview's output and behavior are not described, leaving the agent uncertain about safety.

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 a single, concise sentence. However, it is too brief for a tool with three parameters and no annotations, omitting important details that would justify its length. It achieves conciseness but at the expense of completeness.

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 no output schema, no annotations, and low schema coverage, the description is inadequate. It does not explain the return value, the meaning of 'preview,' or parameter usage, leaving significant gaps for an agent to correctly invoke the tool.

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 add any meaning to the parameters (oid, name, token_ttl_seconds). The schema provides only titles, which are insufficient for an agent to understand parameter usage, such as what 'oid' refers to or how 'token_ttl_seconds' affects the operation.

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 identifies the verb 'Preview deleting' and the resource 'external adapter Hive record,' which distinguishes it from other preview_delete_* siblings. However, it does not explain what 'preview' means in this context, leaving ambiguity about whether it simulates deletion or shows consequences.

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 a direct delete tool or other preview_delete_* tools. There is no mention of prerequisites, conditions, or when-not to use this tool.

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