sync_tracker

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the tracker side is read-only while Yeti item statuses are mutated, but it does not cover permissions, idempotency, overwrite behavior, or what happens when items are unlinked.

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 compact sentences with the core action front-loaded. It avoids waste, though the phrase 'mark them done or open' could be slightly more precise about the status mapping.

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 one-parameter sync tool with no annotations or output schema, the description covers the essential action and the external read-only guarantee. However, it lacks return behavior, error conditions, and prerequisites that would help an agent invoke it confidently.

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 schema has 0% description coverage for the single required projectId parameter. The description only implies that a project is involved and adds no details about the parameter's meaning, expected identifier source, or constraints beyond the schema type.

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 operation: read linked tracker item statuses and mark those items done or open in Yeti. It is clear enough to distinguish as a tracker-to-Yeti sync, though it does not explicitly differentiate itself from siblings such as push_to_tracker or set_project_tracker.

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 explains what the tool does but gives no explicit guidance on when to use it versus alternatives like push_to_tracker or set_project_tracker. It also omits prerequisites such as whether the project must already have a linked tracker.

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