lc_preview_delete_cloud_adapter

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

Without annotations, the description carries the full burden of behavioral disclosure. It says 'Preview deleting,' which implies a non-destructive operation, but it does not explain what the preview returns, whether any state changes occur, or how the result should be used. This lack of detail is a significant gap for a preview action.

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 sentence, which is concise but fails to convey necessary information. It is not verbose, but it sacrifices clarity for brevity. The structure is flat, with no front-loading of critical details.

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?

With 3 parameters, no output schema, and a complex sibling set, the description is too sparse. It does not explain what the preview produces, how to proceed after previewing, or how this tool relates to others like lc_confirm_action. The agent lacks sufficient context to use the tool effectively.

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 coverage is 0%, and the description provides no explanation for any of the three parameters (oid, name, token_ttl_seconds). Despite the low coverage, the description adds no value beyond the tool's purpose. The agent cannot infer parameter meanings or constraints from the description.

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 'Preview deleting a cloud adapter Hive record,' which identifies a specific verb-resource combination and distinguishes from siblings like lc_preview_delete_hive_record (general) and lc_preview_set_cloud_adapter (different action). However, 'preview' is ambiguous—it could mean a dry-run or simulation, but the intent is reasonably clear.

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. Sibling tools include lc_preview_delete_hive_record for general hive records and lc_confirm_action for actual deletion, but the description does not differentiate contexts or state prerequisites.

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