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

Annotations declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, but the description frames the tool as a harmless on/off switch without explaining what turning it off destroys or stops (e.g. whether an existing scheduled refresh is cancelled or whether in-flight sync stops). For a destructive mutation with an open-world side effect on a linked sheet, that behavioral context is missing. Nothing here contradicts the annotations, but the description adds little beyond them.

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?

A single front-loaded sentence with no filler and no redundancy. It is tightly written, though the extreme brevity is also the source of its missing detail.

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 two-parameter destructive toggle with no output schema and zero schema coverage, the description should at minimum state the direction of the boolean and the effect of disabling the check. As written an agent could not confidently call it without inspecting the schema and guessing at semantics.

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 0%, so the description carries the full burden. It hints that 'linked sheet' corresponds to the import_id and that the on/off phrase maps to keepUpdated, but it never states which boolean value means on, nor what form the import identifier takes. Two required, undocumented parameters remain only loosely interpretable from the sentence.

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 gives a specific verb ('turns ... on or off') and a specific resource ('the daily check for new and changed rows on a linked sheet'), so an agent can tell this is a toggle of a cloud-import refresh setting rather than a data-fetch or creation tool. It stops short of distinguishing itself from siblings like list_cloud_imports or preview_cloud_list, but the action itself is unambiguous.

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?

There is no guidance on when to use this versus alternatives, and no prerequisites such as needing an import_id obtained from list_cloud_imports. The agent is not told what conditions should lead it to flip the toggle on versus off.

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