sync_claude_preferences

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the operation is a read-only inventory, ruling out mutation, but it does not address permissions, execution prerequisites, or whether any state is affected; the output schema helps with return format but not with operational behavior.

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 front-loaded sentence with no wasted words. The key scoping information ('read-only inventory') is included alongside the purpose, so the agent can parse it immediately.

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?

Given zero parameters and a present output schema, the description only needs to communicate purpose and safety context, and it does that minimally. It remains incomplete on usage context and on what 'sync candidates' means, which matters for selecting this tool among the many sibling inventory/query tools.

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 tool takes zero parameters, so there are no parameter semantics to document. The description adds no parameter detail, which is appropriate here, and the baseline for a no-parameter tool is high.

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: 'Report Claude Desktop MCP sync candidates,' and adds the qualifier '(read-only inventory).' This distinguishes the operation from a write/sync action and makes the read-only nature explicit, though it does not name a sibling alternative or clarify what a 'sync candidate' actually is.

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 provides no when-to-use guidance, prerequisites, or comparison to alternatives such as list_configured_tools or other inventory tools. The only implied usage comes from the read-only inventory framing, which is too weak to qualify as actual guidance.

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