exec

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

With no annotations, the description carries the full burden. It mentions 'non-interactive' and 'remote' but omits important behaviors such as output handling, exit codes, side effects, privilege requirements, or failure modes.

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 dense sentence, front-loaded with the core action and parameter alternatives. No filler words; every element adds value.

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 complex 9-parameter tool with no annotations, output schema, or parameter descriptions, this is thin. It does not mention return values, error behavior, environment context, or prerequisites, leaving significant gaps for an agent to use it correctly.

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?

All 9 parameters are referenced in the description with usage patterns (alternatives like command/argv/script, optional runtime/script_args/cwd/timeout), adding structural meaning beyond the bare schema. However, it does not explain individual semantics like timeout units or what 'runtime' means.

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 states 'Remote non-interactive exec on ep=' using a specific verb (exec) and resource (ep). It conveys remote command execution and is distinguishable from sibling tools like fs or ps, though it does not explicitly differentiate itself.

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 provides parameter invocation patterns but no guidance on when to use this tool versus alternatives like console or screen. It lacks exclusions, recommended use cases, or contextual selection criteria.

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