neon3_nui_validate

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that the tool parses and compiles and explicitly says it does not submit. However, it does not describe what happens on compile failure, whether there are side effects, or what the response looks like, so transparency is partial.

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 short sentences with no wasted words. The core action is front-loaded, and the critical safety caution 'Never submit automatically' earns its place as a separate, memorable instruction.

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 single-parameter validation tool, the description covers the core action and a key safety constraint. But with no output schema and no mention of result/error semantics, an agent still lacks some context about what a successful or failed validation will actually return.

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. It never explicitly describes the 'source' parameter, though the phrase 'Parse and compile NUI Flow' implies the source should contain NUI Flow content. This is only indirect inference, not clear parameter guidance.

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 uses a specific verb phrase, 'Parse and compile NUI Flow', which clearly names the resource and the action. It also implicitly distinguishes itself from the sibling 'neon3_nui_submit' by ending with 'Never submit automatically,' though it does not explicitly name the alternative.

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 instruction 'Never submit automatically' gives meaningful usage context, implying this tool is a validation/compile step that should not be chained into submission. However, it does not explain when to prefer this over siblings like neon3_nui_inspect or neon3_nui_reference, leaving some routing ambiguity.

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