nexo_skill_result

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

No annotations are provided, so the description carries the full burden. It mentions 'updates trust and promotions' but does not disclose side effects, state changes, idempotency, or required permissions. This is insufficient for a mutation tool.

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, front-loaded with key action. However, it may be too terse given the complexity; every sentence earns its place but could be expanded.

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?

As a result-recording tool that updates trust and promotions, it lacks explanation of what trust is, what promotions entail, and what the parameters mean. No output schema compounds the incompleteness.

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%, so the description should compensate. It hints at 'success' for outcome but adds no meaning for 'id', 'context', or 'notes'. The schema itself has defaults, but description omits parameter semantics.

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 it records the result of using a skill, which distinguishes it from siblings like nexo_skill_apply or nexo_skill_approve. However, 'Updates trust and promotions' is vague without defining trust.

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?

Implies usage for recording skill outcomes but provides no explicit guidance on when to choose this over other tools like nexo_skill_apply or nexo_skill_approve, nor when not to use it.

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