gsc_sync

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

With no annotations, the description must explain behaviors like side effects, auth requirements, or whether the sync overwrites data. 'Sync' implies mutation but lacks details such as whether it's incremental or full, or if it can be safely re-run.

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 one short sentence with no filler. It front-loads the verb and is easy to scan.

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 sync tool with no annotations or output schema, the description under-specifies behavior, including what happens on conflict, expected runtime, or return value. The minimal text leaves many questions unanswered.

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?

The schema already defines site_id, and the description maps to it with 'for a site'. Coverage is 100%, so the description adds minimal extra meaning beyond confirming which site.

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 identifies the action (sync) and resource (Google Search Console data) with a site scope. It distinguishes from sibling analysis tools like gsc_summary and gsc_queries by implying a data transfer operation, though it could be more explicit about what 'sync' entails.

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?

No guidance is provided on when to sync vs. use the other GSC read tools. There are no prerequisites or alternatives mentioned.

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