import_desktop

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

No annotations exist, so description carries full burden. It reveals platform-specific auth (Keychain on macOS, libsecret on Linux) and prerequisite (sqlcipher). Does not specify whether import merges or overwrites existing data, but overall good disclosure for a non-destructive import operation.

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 efficient sentences. First sentence states purpose, second adds prerequisites and auth context, third directs to sibling. Every sentence earns its place with no redundancy.

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 zero parameters and no output schema, description fully covers what the tool does, prerequisites, platform specifics, and alternative tool. Completely adequate for an agent to decide when to invoke.

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 in schema; description does not need to explain parameters. Baseline for zero params is 4. No additional param info is needed.

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?

Clearly states it is a one-time import of all historical messages from Signal Desktop, specifying platform (macOS/Linux). Differentiates from sibling sync_desktop by saying 'for ongoing sync use sync_desktop instead.' Verb+resource+scope are precise.

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?

Explicitly gives guidance: use for one-time import, use sync_desktop for ongoing sync. Mentions prerequisite (sqlcipher) and platform-specific authentication behaviors, which are clear when-to-use/not-use signals.

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