check_nonmem_setup

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

With no annotations provided, the description carries full burden but only states what is checked, not behavioral traits like: whether it returns structured data or plain text, what happens when installations are missing (errors vs warnings), whether it validates executable functionality or just path existence, or if it's safe to run repeatedly.

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?

Single sentence, nine words, front-loaded with the action verb. No redundancy or filler. Every word earns its place in describing the tool's scope.

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 moderate complexity (validating four different software installations) and absence of both output schema and annotations, the description should specify the return format (e.g., report object, status list) and error behavior. It adequately covers the input side but leaves output behavior undocumented.

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 input schema has zero parameters, which establishes a baseline score of 4 per the scoring rubric. The description correctly implies no configuration is needed for this diagnostic check.

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 specific verbs ('Check') and lists exactly which resources are verified (NONMEM, PsN, R, mrgsolve) and what aspects are checked ('installation status and paths'). It clearly distinguishes from siblings like check_psn_status and check_r_setup by covering the full environment rather than individual components.

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?

While the scope (checking four installations at once) implies this is for comprehensive environment validation versus the specific 'check_*' siblings, there is no explicit guidance on when to prefer this over check_r_setup or check_psn_status, or whether this should be run before other operations.

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