sync_saved_notes

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

With no annotations, the description carries the full burden and does so well: it discloses the early-stop behavior of incremental mode, that force soft-deletes local notes no longer saved remotely, the enumerated SyncRun statuses and their meanings, the truncation/rate-limit case, and the required authenticated session with the login remediation command.

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?

Front-loads the core action and mode distinction, and every sentence adds real information. The run-on enumeration of statuses is dense but each item earns its place; minor structural tightening would help.

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?

Complete for a sync tool: auth requirement, both modes, side effects, and failure/partial outcomes are all covered, and although an output schema exists the status enumeration gives an agent what it needs to interpret results.

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 coverage is 0% and the single parameter has no description in the schema, so the description must compensate. It does: it defines the default (incremental, early stop) and the full semantics of force=True, including the soft-delete side effect.

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 (resync) and resource (saved notes from Substack into local SQLite cache), with an explicit scope of incremental vs full. An agent can distinguish this from sync_saved_posts and the other siblings without opening the schema.

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?

Clearly explains the default incremental mode and when to use force=True (full list plus reconciliation/soft-delete). It does not explicitly name an alternative sibling tool, but the mode-selection guidance is explicit enough for correct invocation.

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