alcove_connector_apple_notes_import_local

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

No annotations were provided, so the description carries full burden. It mentions two steps (export and index) but fails to disclose side effects, security implications, performance considerations, or state changes. The description is insufficient for a tool without 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 a single sentence, which is concise but lacks structure. It front-loads the action but does not include any breakdown or additional context. The sentence is too terse to be fully informative, thus it does not earn its place effectively.

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 the complexity (5 parameters, no annotations, 0% schema coverage) and the existence of an output schema, the description is incomplete. It does not mention return values, error conditions, or prerequisites. There are significant gaps that hinder the agent's ability to use the tool 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% and the description does not mention any of the five parameters (home, tags, source_id, workspace, export_dir). The agent receives no help in understanding what these parameters do beyond their names. This is a critical gap.

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 verb 'Export' and the resource 'local Notes.app notes' followed by the action 'into Alcove, then index them'. This distinguishes it from sibling tools like alcove_connector_apple_notes_index, which likely indexes already imported notes, and aligns with the tool's name.

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?

No guidance is provided on when to use this tool versus its alternatives. There is no mention of prerequisites, when not to use it, or any context about the workflow. The description implies importing as a first step, but does not explicitly guide the agent.

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