mdrun_logs

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, which the description aligns with by stating 'Read'. The description adds minimal behavioral context beyond annotations (e.g., implies logs are pre-captured), but does not disclose any additional traits such as rate limits or persistence.

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 one concise sentence, front-loaded with the key action and resource. Every word serves a purpose, and there is no extraneous 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 output schema exists (not shown), the description need not detail return values. However, for a tool with 2 parameters and siblings, it could provide more context on when logs are available and how max_lines is used. It is minimally complete but lacks integration hints.

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%, so the description should explain parameters. It does not mention job_id or max_lines, leaving the agent with only parameter titles from the schema. The description adds no meaning beyond the schema's property names, failing to compensate for the lack of parameter descriptions.

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 tool reads the captured stdout/stderr log for a background simulation. The verb 'Read' and resource 'log' are specific, and it distinguishes from sibling tools like mdrun_status or mdrun_list that serve different purposes.

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 guidance is provided on when to use this tool versus alternatives (e.g., mdrun_status for status, read_text_file for generic files). The description does not mention prerequisites such as requiring a completed simulation or that logs are only available after mdrun_start.

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