Archive or Restore Password

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

Even with annotations present, the description adds substantial behavioral context: it reveals that archiving hides the record from normal views, that the action is reversible, and exactly how to reverse it (`archived: false`). It also labels the operation as Update and impact as Hide/Restore, going beyond the annotation hints.

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 three short paragraphs, each with a distinct role: purpose, usage guidance, and operation class/impact. Every sentence earns its place, and the most critical information is front-loaded in the first sentence.

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 simple toggle tool with two fully described parameters and no output schema, the description covers all necessary aspects: what it does, when to prefer it, how to revert it, and its safety characteristics. An agent can confidently select and correctly invoke this tool based solely on this description.

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 input schema already provides 100% coverage with clear descriptions for both parameters. The description reinforces the `archived` boolean toggle semantics ('true archives; false restores') but does not add significant new parameter-specific meaning beyond the schema. Baseline of 3 is appropriate.

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 opens with 'Archive or unarchive a password,' a specific verb and resource, and immediately distinguishes the action from deletion and from editing password content. It clarifies that archiving hides from normal views and is reversible, making it distinct from sibling tools like hudu_update_password or hudu_delete (if present).

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 explicitly states this is the reversible alternative to deletion and should be preferred when a user wants something 'removed' without permanent deletion. This directly tells the agent when to choose this tool over alternatives, including when not to use it (when permanent removal is intended).

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