submit_batch_job

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

Annotations already communicate that this is a non-read-only, destructive, non-idempotent operation. The description adds useful context about asynchronous execution and the Job Execution service, but it does not disclose the potential side effects of executing arbitrary SAS code or any lifecycle implications.

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 with a front-loaded verb and no wasted words. It delivers the essential information immediately.

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 simple 2-parameter tool with an output schema and annotations, the description is adequate: it states what the tool does and how it executes. It could optionally mention tracking via get_job_status or cancel_job, but those sibling tools make lifecycle management discoverable, so the description is nearly complete.

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 100%, so both parameters (sas_code and job_name) are already documented in the schema. The description itself adds no parameter-level semantics, earning a baseline 3.

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 'Submit' with a clear resource ('a SAS job') and explicit mode ('asynchronous execution via the Job Execution service'). This distinguishes it from sibling tools like execute_sas_code, which likely runs synchronously.

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 description clearly implies this tool is for asynchronous job submission, which is useful context for when to use it versus execute_sas_code. However, it does not explicitly state when not to use it or name alternatives, so it stops short of full guidance.

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