Submit R job

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds no behavioral context beyond the CPU/Rscript framing and does not disclose the dry-run-first workflow or that confirm+dryRun=false are required to actually submit. Nothing contradicts the annotations, but the description carries little weight.

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?

A single front-loaded sentence with no filler, which is well structured. The economy here is partly under-specification rather than tight editing, but as written it is concise and readable.

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 17-parameter submit tool with no output schema and sparse schema descriptions, the description is far too thin. An agent cannot determine submission semantics, resource defaults, or the dry-run confirmation contract from the description alone.

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 17 parameters and only 35% schema description coverage, the description is expected to compensate heavily, and it does not. It mentions only 'project .R file', loosely implying the project and script parameters, and says nothing about cpus, memGb, partition, modules, condaEnv, walltime, or gpuCount/gpuType.

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?

Specific verb ('Run'), specific resource ('project .R file'), and a stated mechanism ('via Rscript') plus scope ('CPU batch job'). This clearly distinguishes it from siblings like ris_submit_python_job, ris_submit_gpu_smoke_test, and ris_submit_array_job without needing to open any schema.

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 when-to-use, when-not-to-use, or alternative guidance is given. Critically, the description omits the dryRun-defaults-true / confirm-must-be-true gate, so an agent reading only the description has no idea a submission requires an explicit two-flag request.

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