import_desktop

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

With no annotations, the description discloses prerequisites and platform behavior (keychain prompts). It lacks details on re-runnability or side effects, but overall is fairly transparent for a simple import 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?

Three sentences with no fluff: first sentence states purpose, second covers prerequisites/platform specifics, third gives alternative usage. 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?

Given no parameters, no output schema, and no annotations, the description covers purpose, prerequisites, platform details, and sibling differentiation. Missing return value or error handling, but acceptable for a one-way import 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?

No parameters exist (schema coverage 100%), so the description need not explain them. Baseline 4 applies.

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 it performs a full one-time import of all historical messages from Signal Desktop, distinguishing it from the sibling tool sync_desktop for ongoing sync.

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 explicitly states prerequisite sqlcipher, platform-specific keychain details, and directs to use sync_desktop for ongoing sync, providing clear when-to-use guidance.

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