lc_preview_unsubscribe_extension

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

With no annotations, the description carries full burden for behavioral disclosure. It implies a non-mutating preview but does not confirm safety, mention required permissions, or describe return format. The word 'preview' suggests dry-run, but this is not explicit.

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?

While the description is short at one sentence, it omits essential information. It is not well-structured because it fails to front-load the most critical details (e.g., that this is a dry-run, how parameters work).

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 annotations and no output schema, the description is severely incomplete. It does not explain the tool's behavior, return values, or parameter semantics. For a tool with three parameters, this level of description is inadequate.

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 provides no explanation for any of the three parameters (oid, extension_name, token_ttl_seconds). An agent must rely solely on parameter names, which are insufficient for correct invocation.

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 unsubscribing) and the resource (org from an extension). It distinguishes from sibling tools like lc_preview_subscribe_extension. However, it does not explain what 'preview' entails, which could lead to ambiguity about whether it is a dry-run or an actual action.

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 lc_preview_subscribe_extension or lc_preview_delete_extension. The description lacks context about prerequisites or typical scenarios for using this preview.

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