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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: only a 'ready' status means the private draft, atomic replacement, or assetId result was actually saved, while errors and pending are not success. This result-interpretation guidance is valuable and not derivable from the annotations.

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 tightly written sentences with the purpose front-loaded and no filler. The second sentence is dense but every clause about success conditions earns its place.

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 explain return values, and it does partially by defining 'ready' as the success state. However, it does not enumerate the full set of possible statuses (e.g. failed, cancelled) or the returned payload shape, leaving gaps for a status-polling 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% and the single jobId parameter is undocumented in the schema, so the description must compensate. 'Owned import job' hints that the jobId must reference a job belonging to the caller, adding some meaning, but it does not clarify format or lookup expectations.

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 an owned import job'), and the 'owned' qualifier distinguishes it from siblings like transfer_document_import_from_app. It is slightly imprecise in that the tool returns status, not the job itself, but an agent can still tell what it does.

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?

There is no explicit when-to-use statement or named alternative, but the status-semantics sentence implies it is used to check the outcome of an import job. Usage is inferable rather than stated, so it lands at minimum-viable.

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