source_sync_drive

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

No annotations are provided, so the description carries the full burden. It discloses that this is a sync operation (implying mutation) and requires user confirmation, which is useful behavioral context. However, it doesn't mention potential side effects (e.g., data overwrites), performance impacts, or error handling, leaving gaps for a tool that modifies data.

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 front-loaded with the core purpose, followed by concise usage guidelines and parameter explanations in a structured format. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 no annotations, 0% schema coverage, but an output schema exists, the description does well by covering purpose, usage, and parameters. It lacks details on behavioral risks (e.g., data loss) and doesn't explain return values, but the output schema mitigates the latter. For a mutation tool, more safety disclosures would improve completeness.

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. It explains both parameters: 'source_ids' as 'Source UUIDs to sync' and 'confirm' as requiring user approval and being 'Must be True.' This adds meaningful context beyond the bare schema, though it could detail format constraints for UUIDs or confirm's default behavior more explicitly.

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') and resource ('Drive sources'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'source_list_drive' or 'source_get_content' beyond mentioning a prerequisite relationship.

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 explicit guidance on when to use this tool: 'Call source_list_drive first to identify stale sources.' It also specifies a prerequisite condition: 'Requires confirm=True' and 'Must be True after user approval,' clearly indicating the context and approval needed before invocation.

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