get_solution_import_status

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

Annotations only give readOnlyHint=true, but the description adds substantial context beyond that: no polling or resubmission, separation of terminal async state from progress and from unavailable/hidden/forbidden evidence, identity readback, and an explicit caution that progress=100 or identity match is not deployment/runtime proof. It also states that no raw job/log/configuration text is returned, which is valuable behavioral disclosure.

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 read operation and its key caveats are front-loaded in the first sentence, and the remaining sentences each add distinct value (evidence separation, ID-relation caution, proof disclaimer, no raw text). It is dense with jargon but earns its length.

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?

With no output schema, the description must describe returns, and it does so reasonably: terminal async state, progress, evidence categories, identity readback, and the absence of raw job/log/configuration text. The main remaining gap is parameter usage guidance for the four ID variants, but the behavioral coverage is otherwise strong for a read-only status 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?

Schema description coverage is 0%, so the description must carry param meaning, and it does so only partially: it refers to 'explicit receipt IDs' and distinguishes async operation IDs from import job IDs conceptually. However, it does not explain alias pairs (importJobId vs import_job_id) or when to supply which ID type, so the semantics remain partly inferred from the schema's anyOf and x-alias-for hints.

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?

States a specific verb and resource: read native asyncoperation and/or importjob by explicit receipt IDs. It also bounds the scope ('once, without polling or resubmission') and names the evidence categories returned, which clearly separates it from siblings like import_solution_async and get_solution_import_log.

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 establishes the usage condition well: call it once with caller-supplied receipt IDs rather than polling or resubmitting. It also warns that caller-supplied IDs are independent observations, not a verified relation, which clarifies interpretation. It stops short of explicitly naming alternatives such as get_solution_import_log or verify_solution_deployment.

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