neon3_nui_submit

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

With no annotations, the description must carry the full burden of disclosing side effects. It describes a two-step behavior (validate, then submit) and implies a write operation, but does not state whether submission is destructive, reversible, or idempotent (despite the idempotency_key parameter). It also lacks details on failure handling or return behavior. The high-level flow is present but shallow.

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 with no filler words, efficiently conveying the main action. However, it is so terse that it sacrifices necessary context for other dimensions. It earns a 4 for brevity, but the structure lacks any breakdown or elaboration where needed.

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 tool with four parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the purpose of ui_endpoint, idempotency_key, or expected_revision, nor what happens after submission. An agent cannot correctly construct a call or interpret results based on this description alone.

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%, so the description must compensate by explaining parameter meaning. However, it mentions none of the four parameters (source, ui_endpoint, idempotency_key, expected_revision). 'source' is presumably the NUI Flow code, but this is never stated. The description adds zero semantic value beyond the schema's bare property names and types.

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 validates NUI Flow locally and then submits it through ui-runtime to the WGPU runtime. It uses a specific verb (validate, submit) and resource (NUI Flow, ui-runtime, WGPU runtime), and distinguishes itself from sibling 'neon3_nui_validate' by explicitly adding submission as part of the pipeline.

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 gives no guidance on when to use this tool versus alternatives. It does not mention 'neon3_nui_validate' or any other sibling, nor does it state when to choose validation-only versus submission. Usage is only implied by the pipeline itself, which is insufficient for an agent to confidently select this tool over its siblings.

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