simulate_xcos_model

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

With no annotations provided, the description carries the full disclosure burden and does not meet it. It does not say that this executes a simulation (implying compute cost and latency), does not mention the default 120s timeout or 10000-sample cap, and does not indicate whether the run has side effects on the model file or workspace.

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?

It is a single tight sentence with no padding, which is structurally fine. However, brevity here comes at the cost of missing information, and the cryptic "TOWS_c" phrasing means the few words used are not maximally informative.

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?

An output schema exists, so return-shape explanation is not strictly needed, but for a 5-parameter simulation tool with 0% schema coverage and no annotations, the description is far too thin. An agent would have to guess at model_path format, sampling behavior, and timeout implications before calling it 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% across 5 parameters, so the description must compensate and largely does not. It hints at duration_seconds ("any positive duration") and outputs ("requested TOWS_c series"), but says nothing about model_path, max_samples, or timeout_seconds, leaving three parameters undefined anywhere in the contract.

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?

"Run a real diagram" gestures at executing a model, but "diagram" and "TOWS_c series" are opaque jargon that an agent cannot map to a concrete action or output. It also fails to distinguish itself from the sibling simulate_first_order_model, which performs a superficially similar job on a specific model type.

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 only guidance is the inline constraint "for any positive duration," which is a parameter rule rather than a when-to-use statement. Nothing says when to pick this over simulate_first_order_model or the inspect/validate siblings, nor are any prerequisites (e.g., model must be loaded or validated first) given.

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