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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the agent knows this is a destructive, idempotent mutation. The description adds that staged data is released and that the sync must be uncommitted, which is useful. It does not describe required permissions, what happens to partially appended chunks, or whether the abort is reversible.

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?

Single sentence, no wasted words, and the key constraint 'uncommitted' is front-loaded with the action.

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 destructive sync mutation with no output schema, the description covers the basic effect but omits important context such as what 'staged data' comprises, whether in-flight chunks are discarded, and how it relates to commit/seal. Annotations cover the safety profile, but the description could be richer for an agent deciding whether to call it.

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 five parameters are already documented. The description adds no parameter-level detail, which is acceptable at high coverage but leaves no extra value.

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 (abort) and resource (hosted graph synchronization) with the scope 'uncommitted' and the effect 'release its staged data'. This distinguishes it from siblings like commit_project_sync, seal_project_sync, and clear_project_graph, though it doesn't explicitly name them.

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 word 'uncommitted' implies this is for abandoning an in-progress sync, which gives some usage context. However, there is no explicit when-to-use versus when-not, no mention of alternatives like commit_project_sync, and no prerequisites or error conditions.

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