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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that: the 'owned job' scoping constraint tells the agent this only works on jobs it owns, and the explicit no-re-evaluation clause confirms reading has no side effects on the underlying import.

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 short sentences, zero filler, and the core action is front-loaded before the exclusion clause. Nothing could be trimmed without losing information.

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?

For a single-parameter read with no output schema, the description gives enough to call it: what it returns (status and receipt) and that it is a pure read. The remaining gap is the ambiguity against the report/output siblings and the unstated origin of job_id.

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 job_id has no description, so the schema contributes nothing beyond the name. The description partially compensates by implying job_id refers to an owned job, but it never says where that id comes from (presumably start_supplier_import or quote_supplier_import) or what form it takes.

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 job's status and receipt'. This distinguishes it from mutating siblings like start_supplier_import, but the word 'receipt' sits ambiguously next to siblings get_supplier_import_report and get_supplier_import_output, and the description never names those alternatives to draw the line.

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 negative clause 'Does not initiate or repeat evaluation' implicitly routes creation/execution to start_supplier_import, which is useful. However, there is no positive guidance on when to pick this over get_supplier_import_report or get_supplier_import_output, so the agent must infer the split from tool names alone.

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