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

The annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), yet the description adds substantive behavior: only "verified saved" results are returned, and it "never starts a solver," which removes ambiguity about side effects on a completed or running run. It also enumerates the artifact categories returned, giving the agent a content model beyond the annotation flags.

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 definition leads with the resource inventory, then adds operating guidance, so the most important content is front-loaded with no filler sentences. "Keep convergence and publication status visible" is terse to the point of being cryptic, which slightly weakens an otherwise tight structure.

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?

Because an output schema exists, the description is not obligated to detail return values, and the annotations plus the "read-only; never starts a solver" line cover the safety profile for a single-parameter read. The gaps are a missing explanation of job_id and the dangling reference to default_artifact_id, which leave the one input under-specified relative to a tool that gates a whole results tree.

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?

The single parameter, job_id, is never mentioned in the description and schema coverage is 0%, so nothing explains its semantics beyond the uuid format in the schema. Worse, the description tells the agent to "Prefer default_artifact_id," a field that does not exist in the input schema, which can send an agent looking for a parameter that cannot be supplied.

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 uses a specific verb-and-resource framing ("List verified saved field files, boundaries, frames, downloads and postprocessing capabilities") and scopes it to "an owned simulation," which is far more informative than restating the name. It does not explicitly differentiate itself from siblings such as view_simulation_result or get_simulation_monitor, so an agent must infer the boundary itself.

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?

"Prefer default_artifact_id for a whole-result view" and "A boundary VTP cannot supply slices or streamlines" give real downstream selection advice, but they address how to use the returned artifacts rather than when to call this tool instead of the sibling viewers. There are no explicit exclusions or preconditions for calling it, so guidance is implied rather than stated.

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