Set sudo password for session

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

The description adds the key behavioral detail that the password is stored 'temporarily', which goes beyond the annotations. However, it does not disclose security implications (e.g., how the password is cleared, if it overrides an existing password, or that it is a sensitive write operation). Since annotations already mark it as non-read-only and non-idempotent, the description adds modest value but lacks depth for a security-sensitive operation.

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 two sentences with no wasted words, and the primary action is front-loaded. It is appropriately concise, though it could be slightly more structured with explicit parameter explanations.

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 security-sensitive tool that sets a sudo password, the description is incomplete. It does not mention how the password is used later, whether it replaces an existing stored password, any session expiry behavior, or the lack of return value (since there is no output schema). The 'temporarily' is helpful but leaves critical operational details unaddressed. Given the complexity of security implications, this is insufficient.

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 lists two parameters (password, sessionId) with no descriptions, and the schema description coverage is 0%. The description does not explain the purpose or format of either parameter, nor clarify that sessionId is likely required despite being marked optional in the schema. This leaves the agent guessing about parameter meaning and requirements.

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 verb 'set' and the resource 'sudo password for session', and adds a clarifying clause about temporary storage for elevated operations. It is unambiguous and distinct from the sibling tools, which are all unrelated (files, metrics, etc.). A slight deduction because 'session' isn't explicitly tied to the sessionId parameter, but the intent is clear.

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 implies usage before elevated operations ('for elevated operations') but does not explicitly state when to call this tool versus alternatives, and there are no direct alternatives. It does not mention prerequisites (e.g., that a session must exist) or when it is unnecessary. Guidance is minimal but not misleading.

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