memory_link_folder

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

With no annotations provided, the description carries the full burden. It discloses that linking causes mirrors to a Git-committable snapshot and that memory syncs across devices. However, it does not mention potential side effects like overwriting existing links, required permissions, or whether the operation is reversible.

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 two sentences: one stating the action and one explaining the benefit. It is concise without fluff. However, it could be slightly more structured by separating the what from the why, but overall it is 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 the tool's complexity (linking a project to a folder for Git sync) and the presence of an output schema, the description covers the core functionality. However, it lacks details about preconditions (e.g., folder must exist, project must exist) and any constraints (e.g., only one link per project). This leaves gaps for an AI agent to know all necessary context.

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?

The input schema has 2 parameters (path required, project optional) with 0% description coverage. The description mentions 'source folder' and 'project' but does not map them to the parameter names or explain their types, formats, or constraints. This leaves ambiguity for an AI agent.

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 action ('Bind a project to a source folder') and the purpose ('for git-synced memory'). It distinguishes from sibling tools by focusing on linking to a folder for Git sync, which is unique among the siblings.

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 indicates when to use this tool: to enable memory to travel with code via git push/pull. It implies the context of multi-device or team collaboration. However, it does not explicitly state when not to use it or compare it to sibling tools like memory_attach_project or memory_make_portable.

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