Check tModLoader dev environment

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

No annotations are provided, so the description must carry full behavioral disclosure. It states what the tool checks, but does not explicitly confirm it is read-only (e.g., 'does not modify anything'), nor does it describe the return format or potential side effects. The implication is a safe check, but not explicitly stated.

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 sentence that is front-loaded with the key action and resource. It is concise and to the point, though it could be slightly more structured (e.g., listing the checks explicitly) without losing brevity.

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 parameter-less validation tool with no output schema, the description provides sufficient context about what is checked and why. It does not explain the return value (e.g., boolean or report), but the purpose is clear enough for an agent to infer 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?

The tool has zero parameters, and schema coverage is trivially 100%. The description adds meaning by specifying the exact items being verified, which helps an agent understand the tool's scope without needing parameter details.

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 uses a specific verb ('reports') and lists the exact components checked ('.NET SDK, ModSources targets file, and mod symlinks'), making the tool's purpose immediately clear. There are no sibling tools for differentiation, but the description is precise enough.

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 phrase 'so a session can tell if the build environment is still in a working state' implies it should be used before building or running, but there is no explicit guidance on when to use this tool versus alternatives (none exist) or exclusions. The usage context is suggested but not clearly stated.

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