memorybank_sync_projects

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

With no annotations, the description carries full burden for behavioral disclosure. It describes auto-recovery behavior and multi-source scanning. However, it does not explicitly state if the tool modifies files outside the registry or if it requires specific permissions, which would enhance transparency.

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 verbose and includes sections and bullet lists, which aids readability. However, some redundancy exists (e.g., repeating 'AUTO-RECUPERACIÓN' in multiple places). It is well-structured but could be more concise.

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, no output schema, and no annotations, the description covers the tool's purpose, usage scenarios, and behavior comprehensively. It lacks detail about the return value or output format, which would improve completeness.

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 zero parameters, so baseline is 4. The description does not need to add parameter information, and it appropriately focuses on the tool's behavior and use cases.

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 synchronizes and auto-recovers projects from multiple sources. It distinguishes itself from siblings by detailing the multi-source discovery and auto-recovery features, which are not mentioned in sibling tool names like memorybank_discover_projects or memorybank_generate_project_docs.

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 scenarios when the tool is useful, such as corrupt registry, indexed code without docs, outdated registry, etc. This gives clear guidance on when to use it versus alternatives.

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