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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false, non-destructive), so the redundant 'Read-only' adds little. However, the description does add real behavioral context beyond annotations: what the response comprises, and that starting a run with an unsupported runner is refused with a 422.

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 dense sentence followed by a two-word tag; the payload contents are front-loaded and every clause carries information (scenarios, policy, history, run_setup, 422). Slightly packed but free of filler.

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 correctly carries the burden of describing the return: scenarios/runners, policy, run history, and run_setup with supported_runners. It is thin on parameter semantics and omits behaviors like not-found handling, but for a simple read tool it is nearly complete.

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 only 33%: organization_id is documented in the schema while agent_id and suite_id are bare strings. The description says nothing about any parameter, not even the optional workspace override or id formats, so it fails to compensate for the coverage gap.

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 names the exact resource ('One simulation suite') and enumerates its contents (scenarios and runners, policy, run history, run_setup), which makes it clearly distinguishable from siblings like list_simulation_suites or get_simulation_run. It is specific but never explicitly contrasts itself with those 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?

Usage is only implied: by exposing run_setup's supported_runners and the 422 refusal, it hints that this call is how you discover which runners are admissible before starting a run. There is no explicit when-to-use or when-to-prefer-an-alternative statement (e.g., versus get_simulation_run).

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