mempalace_sync

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

Beyond the read-only and idempotent annotations, the description discloses that sync never applies in this deployment and explains why (no local project directory). This is valuable context, though it does not specify whether calling the tool errors or returns empty.

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?

A single, front-loaded sentence states the core limitation without redundancy. Every word contributes to the message.

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?

For an unsupported tool, the description, combined with detailed schema and annotations, gives an agent enough information to avoid misuse. It could be more explicit about the expected call outcome, but the overall context is sufficient.

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 already provides thorough descriptions for all three optional parameters, and the tool description adds no additional parameter-specific meaning. With 100% schema coverage, this meets the baseline without compensation.

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 that filesystem sync is unsupported due to missing local project directory, which conveys the tool's non-functional purpose. It distinguishes from siblings by identifying the sync domain, but doesn't describe an active operation.

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 the tool should not be used for filesystem sync because it is unsupported. However, it provides no explicit alternatives or when-to-use scenarios, leaving the agent to infer that this tool should be avoided.

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