Get Spreadsheet Import

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about progress, quota accounting, and bounded row issues, but does not explain permissions, row-bound behavior, or pagination.

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 definition is a single dense sentence with the operation and data scope front-loaded. 'Bounded row issues' is slightly opaque, but there is no wasted framing.

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?

Because there is no output schema, the description reasonably lists the main data categories returned. However, it omits the role of campaign_id and does not clearly position this status tool against the results-oriented sibling, leaving some selection ambiguity.

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% for two required parameters. The description helpfully implies the reference can be a job or handoff identifier and should be reused, but it says nothing about campaign_id and does not clarify the reference object's required type/id structure beyond what the schema itself enforces.

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 read operation over spreadsheet-import status, quota accounting, and row issues. It clearly identifies the resource but does not explicitly distinguish this tool from the nearby get_campaign_creator_import_results sibling.

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 phrase 'using the same job or handoff reference' implies this is a follow-up call after starting an import, but it gives no explicit when-to-use guidance or contrast with get_campaign_creator_import_results, confirm, or cancel.

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