Copy web chats into the vault

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

Annotations only declare destructiveHint=false; the description adds real behavioral context beyond that – the transcript is copied 'WITHOUT deleting them anywhere', the destination is encrypted, and the browser-extension sign-in requirement is stated. It still doesn't say whether copying is idempotent or what happens on re-copy, so not a 5.

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?

Three compact sentences with the copy-vs-delete distinction front-loaded and the prerequisite placed last. Slightly dense, but every clause carries information.

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?

No output schema exists, so the description does need to orient the agent; it covers purpose, non-destructive behavior, destination, prerequisite, and where the result is consumed. It could be more explicit about sibling selection, but it is sufficient for a 2-parameter tool.

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 100%, so both parameters (site enum, chat_id with default 'locked') are already documented, which sets the baseline at 3. The description's note about chat_id='locked' mostly restates the schema rather than adding new syntax or constraints.

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?

States a specific verb and resource ('Saves the full transcript of ChatGPT or Claude chats into the encrypted AppLock vault') and immediately distinguishes the operation from destructive siblings by asserting it copies rather than deletes. An agent can tell it apart from hide_session/hide_browser_chat without opening another schema.

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?

Gives the operative condition ('Use chat_id "locked" for every locked ChatGPT/Claude chat') and a hard prerequisite ('Needs the browser extension with that site signed in'), plus a downstream use case pointing to read_hidden. It stops short of explicitly contrasting when to pick this over a hide/restore sibling, which keeps it at 4.

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