sync_collection

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

No annotations provided; description discloses two-way sync and media default but omits conflict handling, error scenarios, and safety profile. Adequate but not comprehensive.

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 with no redundancy. First sentence immediately states purpose and scope. Every word earns its place.

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?

Adequate given no output schema: explains sync direction and media. Missing authentication guidance and behavioral details like conflict resolution, but not incomplete.

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 covers all 5 parameters with descriptions (100% coverage). Description adds minimal value by restating media default. Baseline score of 3 applies.

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?

Description clearly states the verb 'synchronize' and the resource 'Anki collection', specifying both directions (upload/download) and media inclusion. Distinguishes from siblings as the only sync tool.

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?

Implies usage for syncing collection, but lacks explicit when-to-use vs alternatives, prerequisites (e.g., credentials), or exclusions. No sibling differentiation beyond being the only sync tool.

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