sync

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

The description says the tool refreshes local history, which implies updating or writing local state, while the annotations declare readOnlyHint=true. That is a direct contradiction of the tool's side-effect profile, and the description does not disclose what the force parameter does or what a refresh overwrites.

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 tight sentences with no waste. The core purpose is front-loaded, followed immediately by the usage condition and the contrast with sibling tools.

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 simple two-parameter sync tool with no output schema, the description gives enough context to understand the main use case. However, it leaves the force parameter unexplained and its refresh-local-history wording conflicts with the readOnlyHint annotation, so an agent still lacks important behavioral context.

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 description coverage is 0%, so the description must carry parameter meaning. It explains days partially by saying the last `days` days and giving a 365-day backfill example, but it does not mention the default of 210 or explain the force parameter at all.

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 verb and resource: refresh the local history for a bounded number of days. It also distinguishes this tool from siblings by noting that other tools sync on their own, which clarifies the tool's unique role.

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 explicitly specifies when to use this tool: for a first long backfill such as 365 days, or after watch syncs. It also names the normal alternative behavior, that other tools sync on their own, giving clear routing guidance.

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