import_wait

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

With no annotations, the description fully details polling mechanics, exponential backoff, timeout handling with a structured return, and result summary, leaving little ambiguity about the tool's behavior.

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 paragraph but dense with information, every sentence adds value, and the most critical purpose is front-loaded.

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?

Given 3 parameters, no output schema, and no annotations, the description covers behavior, parameter defaults, output structure on timeout, and result summary, making it fully adequate for confident invocation.

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 coverage is 100% so baseline is 3. The description adds context by mentioning default timeout and source of IDs (imports_list, import_execute), improving parameter understanding beyond raw schema.

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 tool polls import_status until a terminal state, lists all terminal states, and distinguishes itself from siblings like import_status and import_execute by describing the waiting and timeout behavior.

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 implies usage after initiating an import and explicitly mentions re-calling on timeout, but does not explicitly state when not to use or contrast with import_status for snapshot queries. Still, context is clear.

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