source_sync_drive

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

No annotations exist, so the description must disclose behavioral traits. It mentions the confirm requirement but lacks details on side effects (overwriting, rate limits, idempotency, duration). More context would improve transparency.

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?

Three sentences with key points front-loaded. Every sentence earns its place—purpose, prerequisite, and parameter explanation—without wasted words.

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?

An output schema exists, so return values are covered. The description covers prerequisites and required parameter, but lacks detail on behavior when confirm=False (e.g., immediate failure or prompt). Still adequate for a mutation tool with output schema.

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 coverage is 0%, so the description must add meaning. It explains source_ids as 'Source UUIDs to sync' and confirm as 'Must be True after user approval,' providing context beyond the schema's type and default.

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 'Sync Drive sources with latest content,' clearly identifying the verb 'sync' and resource 'Drive sources.' It also mentions a prerequisite (calling source_list_drive), which helps distinguish it from sibling tools like source_add, source_delete, etc.

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?

Explicitly states 'Requires confirm=True' and advises calling source_list_drive first to identify stale sources, providing clear when and how to use this tool versus alternatives.

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