cuemap_project_sync

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly states the tool pushes local-only changes, pulls remote-only changes, and refuses divergent histories or stale concurrent writes. This covers the important safety-critical behavior of refusing conflicts. It does not mention return values or error formats, but the core mutation behavior and its guardrails are transparent.

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?

Two sentences, zero filler. The primary action is front-loaded, followed by the two key behavioral outcomes and a critical approval precondition. Every clause earns its place, making the description easy to parse quickly.

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 sync tool with 3 parameters, no annotations, and no output schema, the description covers the essential context: what it does, how it behaves on divergence, and the approval precondition mapped to the 'confirmed' parameter. It does not describe the return value or what happens on refusal, but the core decision-relevant information is present. Slightly more detail on outcomes would make it fully complete.

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 100%, so the schema already documents all three parameters. The description reinforces the meaning of 'remote' as the exact S3 root and 'confirmed' as an approval flag, but it adds no new semantic detail beyond what the schema properties already state. Baseline 3 is appropriate.

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 uses a specific verb ('Fast-forward') with a clear resource ('a project through immutable history at an S3 sync root'). It distinguishes itself from sibling tools by explicitly describing the push and pull directions, making it obvious this is a bidirectional sync rather than a one-way push/pull. The purpose is unambiguous.

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 implies usage (when you need to synchronize both local-only and remote-only changes) but does not explicitly name alternatives like cuemap_project_push or cuemap_project_pull or state when to choose this over them. The safety precondition 'Use only after explicit approval' is a condition, not a comparative usage guideline. Therefore usage context is implied rather than explicit.

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