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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is fully covered structurally. The description adds one piece of behavioral context beyond that — that evaluations and the linked call are only included 'when available', i.e. the response shape varies by run state — but says nothing about failure behavior for an unknown id.

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?

One short, front-loaded sentence with no filler, and the conditional 'when available' is a meaningful qualifier rather than padding. It is perhaps too terse for what the tool actually returns, but nothing is wasted.

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-param read with full annotation coverage, the description is nearly sufficient, and the mention of evaluations and linked call partially compensates for the absent output schema. It still leaves open whether those fields are omitted or null when unavailable and what happens on a missing/invalid 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?

There is a single parameter with 100% schema description coverage (pattern, length bounds, and 'Resource identifier returned by a previous request'), so the schema carries the semantics. The description adds nothing about the id beyond implying it identifies a run; baseline 3 applies.

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) and resource (a run), and adds that the payload includes evaluations and a linked call, which is more than the name alone conveys. However, it never says 'simulation run' explicitly nor distinguishes itself from siblings like get_simulation or list_simulation_runs, so an agent must infer the relationship.

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?

No guidance on when to use this versus list_simulation_runs (discovery) or get_simulation (parent resource), and no prerequisites such as the run needing to be finished before evaluations exist. The conditional 'when available' hints at state dependence but does not explain it.

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