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

Beyond the destructiveHint annotation, the description adds important behavioral context: owner confirmation is required, prior revisions are retained, there is no automatic merge/fetching/access grant, and a home key header is needed. These are material operational details not present in the structured fields.

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?

Four short, front-loaded sentences with no wasted language. The destructive nature and confirmation requirement are prominent immediately.

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?

The description covers safety, auth, and retention well for a destructive mutation. However, with no output schema and 0% schema description coverage, it leaves key parameter semantics (especially 'revision' and the document payload shape) unexplained for an agent to invoke it correctly.

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% for three required parameters. The description hints that 'document' is a full PAM 1.0 document and that 'confirm_replace' relates to owner confirmation, but it does not explain the meaning or format of 'revision' or the expected document structure.

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 states a specific verb and resource: replacing the current private memory with a full PAM 1.0 document. It is clearly distinct from siblings like home_export or home_remember in practice, though it does not explicitly name or contrast 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?

It gives a clear precondition ('after explicit owner confirmation') and exclusions ('No automatic merge, fetching or access grants'), which help an agent decide when this is appropriate. It stops short of naming alternatives such as home_remember or home_export and when to prefer them.

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