openclaw_skills_install

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

No annotations are provided, so the description must carry the full burden. It mentions mutation and confirmation, but lacks details on overwrite behavior, required permissions, network dependencies, or versioning semantics. Minimal disclosure beyond the fact it modifies state.

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?

Two sentences that efficiently convey the core purpose and a critical behavioral warning. No unnecessary words or repetition.

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?

For a mutation tool with 3 parameters, no output schema, and missing annotations, the description omits key context like return values, error handling, and behavior for already-installed skills. Incomplete for safe agent decision-making.

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 67% (id and instance have descriptions, version does not). The description does not elaborate on any parameters, such as version format or instance routing, failing to compensate for the missing version 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 clearly states the action ('Install a skill') and allows for a specific version. It distinguishes from sibling tools like openclaw_skills_search or openclaw_skills_update, though the internal jargon 'Wraps skills.install' might confuse some agents.

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?

The description warns that it mutates the skill set and advises confirmation, but it does not compare to alternatives like openclaw_skills_update or explain when installation is appropriate versus other operations. No explicit when-not-to-use guidance.

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