archive_asset_password

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

With no annotations, the description carries the full burden of disclosing behavioral traits. 'Archive' implies a state change, but there is no mention of whether it is reversible, what the response looks like, or any permissions required. This is a significant gap for a mutation tool.

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 a single, short sentence with no unnecessary words. It is front-loaded and efficient.

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?

This is a simple tool with one parameter and no output schema, so a minimal description might suffice. However, as a mutation-like operation, the lack of behavioral context (e.g., reversibility, effects) leaves the description only minimally viable.

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 defines 'id' as a required integer, and the description says 'by ID', which confirms the parameter's role. However, with 0% schema_description_coverage, the description should add more detail about what the ID refers to (e.g., password asset ID), though it is somewhat obvious from context.

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 'Archive a Password by ID' clearly states the verb (archive), the resource (Password), and the method (by ID), which distinguishes it from sibling tools like delete_asset_password, unarchive_asset_password, and get_asset_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?

No guidance is provided on when to use this tool compared to alternatives such as delete_asset_password or unarchive_asset_password. The description simply states what it does without explaining the appropriate context or exclusions.

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