get_job_jcl

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the spool-source detail (JESJCLIN/JESJCL/JCL DDs), which is genuinely useful context, but says nothing about truncation behavior, missing/purged JCL, or permissions.

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 short sentences, front-loaded with the purpose before the caveat. The trailing 'Supports custom line limit' is largely redundant with the schema, keeping it just below a 5.

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, read-only, 3-parameter tool with annotations covering safety, this is nearly complete. The remaining gap is that no output schema exists and the description doesn't say what the return looks like (raw JCL lines vs. array) or what happens when JCL is unavailable.

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 jobId, maxLines and environment are already documented, including the server-configuration cap. The description's 'Supports custom line limit' only restates what the schema says, adding no new semantics; baseline 3 applies.

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?

States a specific verb (Retrieve) and resource (the JCL submitted for a job), and even names the spool data sets it reads from (JESJCLIN / JESJCL). It is clearly distinct from get_job_output, though it does not explicitly say so.

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?

Usage is implied — an agent would infer 'call this when you need the submitted JCL rather than job output' — but there is no explicit when-to-use, no exclusion, and no pointer to get_job_output or get_job_status as alternatives.

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