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

The description goes well beyond annotations by disclosing concrete runtime behavior: refusal of cyclic binding sets, rejection of invalid port directions, the timing of validation, the explicit seam assumption about fitness gates, and the cost of one Diagnose-shaped run per model. These details add operational context that readOnlyHint, destructiveHint, and idempotentHint cannot convey.

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 description is dense but each sentence carries unique operational information: composition semantics, validation rules, timing, assumptions, and cost. It is front-loaded with the core action and avoids filler or repetition.

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 pipeline-execution tool, the description covers purpose, constraints, validation behavior, and cost, which is enough to select and invoke it correctly. It is slightly incomplete because there is no output schema and the return-value shape is only hinted at by the mention that the result carries an explicit seam assumption.

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 100%, so the parameters—seed, hours, bindingIds, realizations—are already well documented in the schema. The description mostly reiterates schema wording, such as shared seed/horizon and automatic inclusion of touched models, without adding substantial new parameter-level meaning beyond the structured definitions.

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 opens with a specific verb and resource: 'Run a set of stored Bindings (see sim_bind) as a composed pipeline.' It further explains the mechanics—topological order and trajectory resampling—so an agent can distinguish this from other sim_* tools. Referencing sim_bind and sim_compare strengthens differentiation from 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?

The description provides clear context for when this tool is appropriate: after bindings are stored via sim_bind, and when composing models under the same discipline sim_compare enforces within one model. It also explains that port validation happens here, not at sim_bind time. However, it does not explicitly state when not to use it or name a direct alternative.

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