sync_status

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description reinforces them with 'Read-only' and 'No side effects'. It adds useful context by explaining the tool reports pending operations from add_memory calls and describing the return values, which goes beyond the annotations.

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 economical and front-loaded: it opens with the core purpose, then adds the specific use case, safety characteristics, and return behavior in a few short sentences. Every sentence earns its place without redundancy.

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 read-only status tool, the description is complete: it explains what the tool does, when to use it, that it has no side effects, and what it returns. Since there is no output schema, the explicit return description fully covers the agent's need.

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 has zero parameters, so there is no schema burden to compensate for. The description adds relevant semantic context about what the tool reports and returns, making the no-parameter interface entirely self-explanatory.

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 checks the background job queue and sync status, and specifically ties it to pending async operations from add_memory calls. This distinguishes it from siblings like cache_stats and get_memory by focusing on write verification rather than data retrieval or cache management.

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 explicitly says 'Use to verify all writes completed', giving a clear context for when to call the tool. It does not name specific alternatives or exclusion conditions, but the intended use case is unambiguous enough for an agent to select it appropriately.

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