Import / sync sessions

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

Annotations indicate readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the description adds value by detailing that it imports new sessions, optionally refreshes existing ones, and returns counts of imported/refreshed/skipped. It does not contradict annotations.

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 well-structured with a purpose paragraph followed by parameter and return details. It is front-loaded and each sentence adds value, though slightly verbose with the enumeration of trigger phrases. Still concise overall.

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 2 simple parameters and full schema coverage, the description explains the return value (counts) and provides context about auto-import. It is sufficiently complete for effective use, though no output schema exists to describe detailed response structure.

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% with descriptions for both parameters. The description adds meaning beyond the schema by explaining defaults ('default all', 'default false'), behavior ('limit to one source', 'refresh in place'), and the return value. This exceeds the baseline of 3.

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 the tool scans local AI-tool history and imports new sessions into Mind Map, specifying the verb 'import', resource 'sessions', and scope across multiple sources. It distinguishes from siblings like mindmap_list or mindmap_search, which serve different purposes.

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?

The description provides explicit example phrases triggering use ('import my sessions', 'sync mind map') and contrasts with periodic auto-import as an alternative. However, it lacks explicit guidance on when not to use it or direct comparison with other siblings.

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