cst_get_simulation_status

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

No annotations provided. Description states what is returned but does not mention side effects or behavior (e.g., read-only, requires active simulation). Additional context like 'does not modify simulation state' would improve transparency.

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?

Two sentences, front-loaded with purpose and key return details. No wasted words, every sentence adds value.

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?

Tool is simple with no parameters or output schema. Description sufficiently covers purpose and return values, making it complete for an agent to understand usage.

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?

No parameters exist; schema coverage is 100% (vacuously). Baseline score of 4 is appropriate as description adds no parameter info needed.

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?

Clearly states the tool checks status and progress of a running CST simulation. Lists specific return information (running, progress, mesh, time step), distinguishing it from siblings like run, pause, stop, and solver info tools.

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?

Implicitly indicates use after starting a simulation, but lacks explicit guidance on when not to use it or alternatives (e.g., cst_get_solver_info for solver-specific details). No exclusions mentioned.

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