sync_saved_posts

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

With no annotations, the description carries the full burden. It discloses that the tool writes to a local SQLite cache, requires authentication, and supports two resync modes. This is meaningful behavioral context, though it could mention potential side effects like cache overwriting or duration.

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 two sentences, front-loaded with the core purpose and a necessary prerequisite. Every word contributes value; no redundant details.

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?

The tool is simple (one optional boolean, no required params) and an output schema exists. The description covers purpose, prerequisite, and side effect, which is adequate. It could elaborate on what 'resync' entails (e.g., network usage, cache overwrite) but is largely complete for its simplicity.

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 input schema only lists a boolean 'force' with 0% description coverage. The tool description hints that 'incremental or full resync' relates to this parameter, adding meaning. However, it does not explicitly map 'force' to either mode, leaving some ambiguity.

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 identifies the action ('Trigger... resync'), the resource ('saved posts from Substack account'), and the destination ('into local SQLite cache'). It also mentions the two modes (incremental/full), which distinguishes it from siblings like list_saved_posts that likely just read the cache.

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 states a prerequisite ('Requires an active authenticated Substack session') but does not explicitly contrast it with alternative tools or describe when to choose incremental vs full resync. The intended usage is implied rather than explicitly guided.

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