lc_preview_set_ai_skill_enabled

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

The term 'Preview' is ambiguous—it could imply a dry-run or an actual toggle. The description does not clarify side effects, whether the action is reversible, or if authentication is needed. With no annotations, the transparency is insufficient.

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, effectively concise. However, it sacrifices necessary detail for brevity.

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 4 parameters and no output schema, but the description omits return behavior, confirmation of success, or relationship to the broader AI skill lifecycle. Incomplete for effective use.

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 explanation for parameters (oid, name, enabled, token_ttl_seconds). The agent receives no guidance on what values to provide.

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 toggling) and the resource (AI skill Hive record's enabled metadata), distinguishing it from broader tools like lc_preview_set_ai_skill.

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 alternatives such as lc_preview_set_ai_skill or other preview_set_X_enabled tools. No prerequisites or context provided.

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