Prepare login-node command

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

Description says 'Preview' suggesting a non-destructive read-only operation, but annotations have destructiveHint=true and readOnlyHint=false. This is a critical contradiction, and no additional behavioral details are provided to clarify the actual side effects.

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 concise sentences, front-loaded with the primary purpose and a useful constraint. No wasted words, though the term 'constrained' is ambiguous.

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 tool has six parameters, no output schema, and annotations that contradict the description, the text is far from complete. It doesn't explain what 'preview' means mechanically, expected output, or how it differs from validate_job or render_job.

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?

With schema description coverage of 0%, the description carries no parameter information. None of the six parameters (executable, cwd, args, env, modules, timeoutSeconds) are mentioned or explained in the text.

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?

Purpose is clear: 'Preview a constrained build or pre/post-processing command' identifies a specific action and resource. It distinguishes from submit_job by noting heavy computation must be submitted as a job.

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?

Explicitly states 'Heavy computation must be submitted as a job,' providing a clear exclusion for when not to use this tool. It implies this tool is for lightweight, preview-only commands, though it doesn't name an alternative tool explicitly.

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