sync_review

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

readOnlyHint=true is consistent with "List", so no contradiction. The description usefully adds the "local" scope (as opposed to cloud-oriented siblings) and that results are constrained by existing policy, but it says nothing about volume, pagination, or what a candidate record looks like beyond the implied scope.

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?

A single tight sentence with the scope front-loaded and no filler. It is efficient, though the brevity edges toward under-specification rather than deliberate concision.

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?

No output schema exists, so the description should explain what a "sharing candidate" is and what the initiative parameter selects; it does neither. Combined with the mismatch between the name and the described behavior, an agent lacks what it needs to call this 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?

There is one required parameter, initiative, with 0% schema description coverage, and the description never mentions it. An agent must guess whether initiative is a name, an ID, or a scope selector, so the description fails to compensate for the schema gap.

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 has a specific verb and object ("List local sharing candidates") plus a scoping phrase ("under existing policy"), which is more than a tautology. But it does not reconcile with the tool name sync_review, and it never distinguishes this listing from siblings such as share, policy, or review, leaving an agent unsure whether this enumerates or triggers anything.

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?

No when-to-use, when-not-to-use, or prerequisite guidance is given. With siblings like share, unshare, policy, and cloud_links in the namespace, the description offers no routing signal about when an agent should pick sync_review over any of them.

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