source_sync_drive

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

Since no annotations are provided, the description carries full burden for behavioral disclosure. It mentions the confirm=True requirement (a safeguard), but lacks details on idempotency, error handling, auth prerequisites, or potential side effects of syncing.

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 concise sentences front-loaded with the essential action and requirement. Every sentence adds value without redundancy.

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 the tool has an output schema (not shown), return value details are not needed. The description covers the main workflow step. However, missing details about conflict resolution or error scenarios slightly reduce completeness for a mutation tool.

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 100% with descriptions for both parameters in the input schema. The description adds value by requiring confirm=True and linking source_ids to source_list_drive, providing beyond-schema context.

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'), the resource ('Drive sources'), and the scope ('with latest content'). It also specifies a critical requirement (confirm=True) and provides a precursor step, distinguishing it from siblings like source_list_drive and source_add.

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?

It explicitly tells the user to call source_list_drive first to identify stale sources, providing clear context for when this tool is appropriate. However, it does not explicitly state when not to use it or list alternatives, leaving some room for ambiguity.

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