mdrun_status

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

The description adds 'return progress plus log tail' beyond the annotations, which already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. No contradictions.

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 a single, clear sentence. It is front-loaded and contains no redundant information.

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?

Given the simple nature of the tool (1 parameter, output schema exists, annotations present), the description is largely complete for its purpose, though it could elaborate on the meaning of 'progress' and 'log tail'.

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?

Only one parameter 'job_id' exists, but the description provides no additional meaning beyond the schema. With 0% schema description coverage, the agent must infer from the parameter name alone.

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 clearly states the verb 'check' and the resource 'background simulation', and specifies the return value 'progress plus log tail'. This distinguishes it from sibling tools like mdrun_start and mdrun_stop.

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 explicit guidance on when or when not to use this tool. It is implied that it should be used after starting a simulation, but no alternatives or prerequisites are mentioned.

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