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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true. The description adds real context beyond them by noting that the import can poll the source daily for new and changed rows, which explains the recurring-sync behavior. However, it never explains what the destructive behavior actually does, such as whether existing imported rows are replaced or overwritten, so part of the burden remains unmet.

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?

Two short sentences with the primary action front-loaded, and no filler. It is efficient, but its brevity is also the source of the coverage gaps rather than a virtue earned by covering the essentials.

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?

This is a 10-parameter, destructive, open-world import tool with a nested object parameter, and it has no output schema and no annotations beyond safety hints. The description does not explain the required identifiers, the mapping structure, or what the returned import looks like, so it is well short of what an agent needs in order to call this tool correctly.

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% across 10 parameters, including the nested 'mapping' object, so the schema alone explains almost nothing. The description compensates for only one parameter, the daily-check behavior implied by keepUpdated, and says nothing about connection_id, import_id, link, sheet_id, identity_column, source_sha256, or how mapping works, which is a substantial gap.

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 states a specific verb and resource set: it imports a Google Sheet, Excel workbook, or Airtable view, and it explicitly names three supported source types. It does not, however, distinguish itself from close siblings in the list such as import_csv, preview_cloud_list, or update_cloud_import, so an agent still has to infer why it should pick this tool over those.

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 offers no guidance on when to use this tool rather than alternatives, and it names none of the obvious siblings. The only usage hint is the vague phrase 'can also check the source every day,' which does not tell an agent when to enable that behavior or when a one-time import is preferred.

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