Start a long-running command as another Linux user

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

Without annotations, the description covers key behaviors: asynchronous execution (returns jobId), sudo -iu invocation, password handling via stdin with no logging. Missing: side effects, error conditions, timeout behavior, or return value format beyond jobId.

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 sentences: first states the primary action and key output (jobId), second references sibling tools and highlights password security. No fluff, front-loaded.

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?

No output schema or annotations, so description must carry the full burden. It explains core behavior but omits details like error handling, authentication needs, or exact response structure. Adequate for simple usage but not robust for an AI agent.

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 coverage is 57% (4 of 7 parameters have schema descriptions). The description adds value for sudoPassword (piped stdin, not logged) but doesn't elaborate on other parameters beyond schema. Since schema covers some, description is adequate but not compensating for the 43% uncovered.

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 starts a long-running command as another user via sudo, returns a jobId immediately, and distinguishes itself from siblings like exec_status and exec_cancel. The verb 'Start' and resource 'long-running command' are specific.

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 tells the agent to use exec_status to read output and exec_cancel to stop the command. It explains that the password is never logged, but does not explicitly explain when not to use this tool versus exec_as or exec_start (e.g., synchronous alternatives).

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