monitor_import_set_progress

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

In absence of annotations, the description discloses polling behavior and a 5-minute timeout, but does not state whether the operation is read-only or has side effects, nor mention rate limits or impact.

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 two sentences, no filler, front-loaded with key information, and efficiently conveys purpose and usage.

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?

While the description covers purpose and timeout, it omits the return value (expected progress information) and does not document the parameter, leaving an agent without complete context for a simple monitoring tool.

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 fails to mention the 'max_wait_seconds' parameter or explain its role, despite referencing the default timeout implicitly.

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 active import set runs until completion or timeout, and explicitly provides usage context ('Use after kicking off a bulk migration'). This distinguishes it from siblings like 'run_full_migration' or 'check_migration_state'.

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 gives a clear when-to-use hint ('after kicking off a bulk migration'), but does not specify when not to use or mention alternative monitoring tools (e.g., 'check_migration_state', 'verify_migration_counts').

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