Sync All Properties

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it's an asynchronous operation (returns immediately with a job ID), handles up to 2 properties in parallel for performance, and requires follow-up with 'check_sync_status'. However, it doesn't mention potential rate limits, authentication requirements, or error handling.

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 perfectly concise with three sentences that each earn their place: first states purpose and scope, second explains performance characteristics, third describes return behavior and monitoring. It's front-loaded with the core functionality and wastes no 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 the tool's moderate complexity (asynchronous batch operation), no annotations, and no output schema, the description does well by explaining the asynchronous nature, parallel processing, and monitoring requirement. However, it doesn't describe what data gets synced beyond 'search analytics data' or potential limitations (e.g., property count caps, data freshness).

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 100%, providing detailed documentation for all 4 parameters. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting. No compensation is needed given the high coverage.

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 specific action ('Sync search analytics data'), the resource ('ALL accessible GSC properties'), and the scope ('in one call'), distinguishing it from sibling tools like 'sync_gsc_data' which likely handles individual properties. The verb 'Sync' is precise and the resource scope is explicitly defined.

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 explicitly states when to use this tool ('for ALL accessible GSC properties in one call') and provides a clear alternative for monitoring progress ('use check_sync_status to monitor progress'), distinguishing it from siblings like 'sync_gsc_data' (implied for single properties) and 'cancel_sync' (for stopping operations).

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