store_password

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

No annotations are provided, so the description carries full burden. It discloses encryption and one-time nature, but fails to explain behavior on repeated calls (overwrite?), required permissions, side effects, or security guarantees. For a sensitive operation, more detail is needed.

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 are concise, but the description is under-specified for a security tool. The structure is adequate, but could include more details without exceeding reasonable length.

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 presence of sibling tools and output schema, the description lacks completeness. It does not explain what the tool returns, error conditions, or how it fits into the sudo workflow (e.g., required before sudo_exec). A more complete description would link to siblings.

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 0%, and the description adds no meaning to the 'password' parameter beyond the schema's type and requirement. No constraints, format, or security hints are provided, leaving the agent without guidance on valid input.

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 'Store sudo password encrypted', specifying the verb and resource. It distinguishes from siblings like 'clear_password', 'has_password', and 'sudo_exec' by implying a setup action, though not explicitly contrasting them.

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?

Only mentions 'Only needs to be done once', which hints at a one-time setup but provides no explicit guidance on when to use this tool versus alternatives like 'has_password' (to check existence) or 'sudo_exec' (to use the password). No prerequisites or conditions are stated.

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