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

The readOnlyHint=false annotation already signals a mutating operation, and the description adds that calls are vaulted, policy-gated, and produce child-node crystallization in e.mem. It still omits important behavioral details such as what policy denial looks like, whether external side effects are reversible, and what the caller should expect after dispatch.

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 compact sentence with no filler. It is somewhat front-loaded with 'Vaulted, policy-gated actuation' rather than a direct verb, and the e.mem clause is cryptic, but the overall structure is efficient.

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?

This is a mutating tool with a nested, property-less payload object and no output schema, so the description needs to explain payload shape, expected results, and failure modes. Instead it gives only a high-level gloss and leaves the agent without enough operational context to invoke it confidently.

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 100%, so the schema already documents the surface, action, and payload parameters. The description restates some surface names but actually omits 'notion' and 'icx_memory', which appear in the schema, and it adds no payload-shape or action-syntax detail. Baseline 3 is appropriate when structured fields carry the 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 indicates dispatching actions into external tools and lists several target surfaces, so the general purpose is inferable. However, the core verb 'actuation' is jargon, and the 'child-node crystallization in e.mem' clause muddies what the tool actually does. It also does not distinguish this from siblings such as icx_exec or icx_wasm_exec.

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?

There is no explicit guidance on when to use this tool versus alternatives like icx_exec, icx_wasm_exec, or icx_remember. The phrase 'policy-gated' hints at prerequisites, but the description does not state selection criteria or exclusions.

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