source_sync_drive

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

With no annotations provided, the description carries the full burden. It discloses an important behavioral requirement: 'Requires confirm=True' and clarifies that it must be set after user approval, implying the operation has side effects. It also hints at the sync behavior via 'latest content' and the prerequisite workflow, but could be more explicit about what synchronizing does (e.g., overwrite local data or pull from Drive).

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?

The description is concise and well-structured. It leads with the purpose, then the requirement, a prerequisite, and an Args list. Every sentence earns its place, with no redundancy or filler.

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 tool with only 2 parameters, one required, and an output schema, the description is fairly complete. It covers purpose, prerequisites, parameter meanings, and a safety requirement. The only minor gap is lack of explicit clarification on what happens during sync (e.g., whether it is incremental or overwriting), but the output schema likely covers return values, so the description is sufficient.

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 0%, so the description must compensate. The Args section adds meaning: 'source_ids: Source UUIDs to sync' and 'confirm: Must be True after user approval.' This goes beyond the raw schema types, explaining what each parameter is for and the constraint on confirm, though it could provide more detail on edge cases or formats.

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 clearly states the action: 'Sync Drive sources with latest content.' This is a specific verb ('sync') and resource ('Drive sources'), distinguishing it from sibling tools like 'source_list_drive' (which lists sources) and 'source_delete' (which deletes).

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 gives a concrete usage guideline: 'Call source_list_drive first to identify stale sources.' This implies the tool should be used after listing and identifies a prerequisite. It could be stronger if it explicitly stated when not to use it or named an alternative, but it provides clear workflow context.

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