sudo_exec

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the command runs with sudo, but does not disclose side effects (e.g., elevated privileges, potential system changes), failure modes (e.g., timeout, permission errors), or dependencies (e.g., stored password existence). More detail is needed for safe usage.

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 very concise: two sentences plus a structured Args list. Every line serves a purpose. No extraneous information.

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?

Given the tool's complexity (sudo execution) and the presence of an output schema (but not described), the description is minimally adequate. It lacks context about prerequisites (password must be stored), error behavior, and security implications. However, it covers the basic purpose and parameters. More detail would improve completeness.

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 explains both parameters: 'command' is a shell command string, and 'timeout' is an integer defaulting to 120 seconds. This adds clear meaning beyond the schema's property names and types. However, it could be more specific (e.g., timeout is in seconds, not milliseconds).

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 executes a command with sudo using the stored password. It uses a specific verb 'execute' and identifies the resource as a command with sudo. This distinguishes it from sibling tools that manage passwords (clear_password, has_password, store_password).

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., password must be stored) or situations where a different tool (like a non-sudo command executor) should be used. Sibling tools are about password management, so usage context is implied but not explicit.

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