sync_gsc

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

The description indicates that the operation is 'durable' and requires 'user approval,' which provides some behavioral context. However, without annotations, it fails to disclose side effects, required permissions, or what happens after queuing (e.g., asynchronous progress). The existence of an output schema is not mentioned.

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 a single sentence, making it very concise. However, it is too brief to cover necessary details, and it does not use a front-loaded structure to convey key points efficiently.

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?

Despite having only one parameter and an output schema, the description is insufficient for correct tool invocation. It omits information about how to get the connection_id, what the output contains, and whether there are prerequisites like approval flow. Sibling tools are not referenced to fill gaps.

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?

With 0% schema description coverage, the description must compensate. It neither explains what connection_id represents nor how to obtain it. The term 'one GSC property' is ambiguous and not linked to the parameter, leaving the agent without guidance on providing the correct input.

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 (queue a durable refresh), the resource (one GSC property), and a condition (after user approval). It distinguishes this from sibling tools like list_gsc_connections and query_gsc by focusing on refreshing rather than listing or querying.

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 use this tool versus alternatives such as list_gsc_connections (to find connection IDs) or query_gsc (to fetch data without refresh). There is no mention of prerequisites or scenarios where queuing a refresh is appropriate.

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