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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description's only added behavioral detail is the 'owner-scoped' access constraint, which hints at permission boundaries but says nothing about pagination, retention, or error behavior when the job is unknown.

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?

A single short sentence with the resource and scope front-loaded and zero filler. Nothing is redundant or padded.

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 one-parameter read-only tool with full annotations and no output schema, the description is minimally viable. It falls short only on explaining the jobId's origin and its relationship to the export artifact/manifest tools, which an agent needs to sequence calls correctly.

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 required parameter 'jobId' is undocumented in both the schema and the description. The description does not say where the jobId comes from (presumably evidence_create_export) or that it is an opaque identifier, leaving the only input to the tool unexplained.

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 ('Read'), resource ('export job status'), and cardinality/scope ('one owner-scoped'), which distinguishes it from the plural list tools and from evidence_create_export. It does not, however, explicitly differentiate itself from evidence_get_export_artifact or evidence_get_export_manifest, which are the nearest siblings.

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 when-to-use guidance and no routing to alternatives. An agent cannot tell from the description whether to call this before or after evidence_get_export_artifact, or under what job state it is useful.

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