get_job_info

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

No annotations are provided, so the description carries the full burden. It only says 'get job information and spool files' without explaining what information is included, whether spool files are returned as content or references, or any behavioral details like authentication or side effects. This is insufficient for a tool with no annotations.

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 that gets to the point. It is efficient, though it could benefit from a bit more detail without becoming verbose. It earns its place by being direct.

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 tool with 2 parameters and no output schema, the description is minimally adequate. However, it lacks clarity on what 'spool files' means (e.g., metadata or content) and does not explain the optional 'jobmask' parameter. Given the sibling 'download_job_spool', the description should clarify the relationship.

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 0%, meaning no parameter descriptions are provided. The description does not explain the meaning or format of 'jobid' or the optional 'jobmask' parameter, leaving the agent without guidance on how to fill in the arguments correctly.

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 clearly states what the tool does: 'Get job information and spool files for a specific job ID'. It uses a specific verb and resource, and distinguishes from siblings like 'download_job_spool' (which downloads a spool file) and 'list_jes_jobs' (which lists jobs).

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 guidance is provided on when to use this tool versus alternatives. It does not specify when to prefer this over 'download_job_spool' for spool files or 'list_jes_jobs' for job listings. Usage context is only implied by the tool's purpose.

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