source_sync_drive

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

No annotations exist, so the description carries full burden. It reveals the confirmation requirement and sync action, but omits details about side effects, reversibility, or error behavior. For a mutation tool without annotations, more behavioral depth would be expected.

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 concise, front-loaded sentences. Every sentence adds value: main action, prerequisite, and parameter explanation. No 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?

Given an output schema exists (context signal), the description need not detail return values. It adequately covers prerequisites and required parameters, leaving no obvious gaps for a sync tool with a supporting sibling.

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%, but the description adds meaning for both parameters: source_ids as 'Source UUIDs to sync' and confirm as 'Must be True after user approval.' This compensates well for the lack of schema descriptions.

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 starts with a clear verb+resource: 'Sync Drive sources with latest content.' It immediately states the tool's primary action on a specific resource, and hints at differentiation by mentioning a prerequisite sibling tool (source_list_drive).

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?

Explicit usage guidance: 'Requires confirm=True' and 'Call source_list_drive first to identify stale sources.' This tells the agent when to use this tool (after listing drive sources) and a necessary condition (confirmation), making it highly actionable.

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