nexo_skill_apply

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

The description mentions execution goes through the stable nexo scripts runtime, which adds some behavioral context. However, it does not disclose potential side effects, authorization needs, or whether it is destructive, leaving significant gaps given the absence of annotations.

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 two sentences, front-loading the core action and mode selection. It is concise with no wasted words, though it could be slightly expanded to include parameter hints.

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 five parameters, no output schema, and many sibling tools, the description fails to provide sufficient guidance on usage, parameter roles, or expected results. It is too minimal for effective agent invocation.

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?

Parameter descriptions are absent in both the schema (0% coverage) and the description. The description does not explain what 'params', 'mode', 'dry_run', or 'context' mean or how they affect execution, so it adds no value beyond the raw schema.

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 tool applies a skill in one of three modes (guide, execute, hybrid). This distinguishes it from other skill tools like creation or approval, but it does not explicitly contrast with siblings like nexo_skill_test or nexo_skill_result.

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. There is no mention of prerequisites, contexts, or decision criteria for selecting this tool over other nexo_skill_* tools.

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