sync

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

No annotations are provided, so the description carries the full behavioral burden. It says the tool refreshes memory and re-reads changed files, but it does not disclose side effects, idempotency, permissions, whether existing memory is overwritten or merged, or what happens on partial failure.

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?

Three short sentences, front-loaded with the core action, and no wasted wording. The no-argument constraint is stated directly and reinforces the scope.

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 zero-parameter tool with no output schema and no annotations, the description explains the basic scope but omits sibling differentiation and sufficient behavioral detail for a refresh operation. An agent can call it correctly, but cannot confidently choose it over sync_all.

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 tool takes zero parameters, which sets the baseline at 4. The description appropriately confirms this by stating it takes no arguments and can only refresh what the server owner has already configured.

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 states a specific operation: refresh memory from configured sources, run every server connector, and re-read changed import files. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools like sync_all or the per-source sync_* tools.

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?

It implies usage by saying it refreshes everything already configured and takes no arguments, so it cannot target arbitrary sources. However, it does not state when to use this instead of sync_all or individual sync_* tools, nor does it name any alternatives.

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