memory_mesh_sync

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: it discloses required authentication, peer reachability constraints, default direction, the write effects of push vs. pull ('push sends local data; pull merges received records'), local state mutation ('Updates local peer/audit state'), and partial-failure behavior ('returns per-peer pushed/pulled counts and errors, even when some peers fail').

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 front-loaded with purpose and prerequisites, and every sentence contributes useful context. It is slightly redundant in restating parameter defaults already present in the schema, keeping it just short of ideal conciseness.

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 a parameter-light but behaviorally complex synchronization tool with no output schema and no annotations, the description is complete enough: it covers purpose, prerequisites, peer selection, direction semantics, side effects, return information, and failure handling.

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 already 100% and documents both parameters, so baseline is 3. The description adds operational meaning beyond the schema by explaining the effect of each direction value ('push sends local data; pull merges received records') and by clarifying that omitting peerId selects all peers.

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?

States a specific verb ('Exchange') and resource ('configured shared collections with registered peer AgentMemory instances'), making it clear this is peer-to-peer synchronization rather than a local memory operation. However, it does not explicitly name or distinguish itself from any sibling tool, so sibling differentiation is implicit rather than stated.

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?

Provides clear prerequisites ('Requires AGENTMEMORY_SECRET and reachable permitted peer URLs') and a restriction ('Use only for authorized peer transfers'), which gives context for appropriate use. It does not, however, name alternative tools or describe when another sync/share tool would be preferable.

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