refresh_memoreei

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

No annotations are provided, so the description carries the full disclosure burden. It states the tool triggers an outward-facing sync but never says whether it blocks, how long it takes, whether it is rate-limited, whether re-running is safe, or whether it can fail on unreachable sources — meaningful gaps for a network-triggering operation.

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 sentence with the action, scope, and outcome front-loaded in that order. No filler, no restatement of the tool name, nothing that could be cut.

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?

With no output schema, the description usefully compensates by naming the return value ('new message count'). Combined with zero parameters and a stated scope, an agent has enough to call it, though blocking behavior and failure modes remain undocumented and there are no annotations to cover them.

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, so there is no parameter semantics to explain and the baseline is 4. The description correctly avoids inventing parameters and instead spends its words on scope and return value.

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 names a specific action ('Trigger an immediate sync'), its scope ('all configured sources'), and its return value ('new message count'). It is clear what the tool does, but it offers no differentiation from the heavy cluster of sync siblings such as sync_all and sync, which appear to overlap with the same 'sync everything' semantics.

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?

There is no guidance on when to prefer this over sync_all, sync, or the per-platform sync_* tools. The agent is left to infer that a tool literally named for a product refresh is distinct from the near-identical 'sync all configured sources' siblings, with no exclusions or alternatives stated.

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