nexus_exec

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

Annotations are minimal (only openWorldHint), so the description carries the transparency burden. It does disclose notable behaviors: ring-buffer output, secret redaction, and process-group kill on timeout. However, it omits important safety semantics such as the requirement to set allowDangerous for dangerous commands, and it doesn't describe background execution behavior.

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 compact and efficient—just two sentences that front-load the primary action and then list key features. No redundant or filler content. Every word contributes to understanding.

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?

Despite its apparent simplicity, the tool has complex behaviors (timeout, ring-buffer, secret redaction, background jobs, allowDangerous) and no output schema. The description does not clarify return values, output format, polling implications (especially with nexus_exec_poll as a sibling), or failure modes. This makes the description under-specified for reliable use.

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?

The schema already describes 4 of 5 parameters with meaningful text. The description adds 'timeout' which aligns with timeoutMs, but this is a generic mention. It does not enrich understanding of args, background, or allowDangerous beyond their existing schema descriptions. Overall, the description adds modest value for parameters.

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 'Run a command' and lists specific behaviors: timeout, ring-buffer output, secret redaction, and process-group kill. This makes the tool's purpose unambiguous, but it does not explicitly contrast with sibling tools like nexus_test_run or nexus_exec_poll, so it lacks direct sibling differentiation.

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 offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites, likely use cases, or exclusions. The only contextual signal is the openWorldHint annotation, which is not elaborated. Users are left to infer when nexus_exec is appropriate.

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