get_job_status

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

With no annotations, the description carries the behavioral burden. 'Get the current status' clearly indicates a read operation that returns a snapshot rather than mutating state. However, it does not mention whether the job is removed after retrieval, whether the endpoint is safe to poll repeatedly, or what happens if the job ID is invalid.

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 one sentence, front-loaded with the action, and contains no redundant information. The example adds clarity without bloat.

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 only one required parameter and an output schema, the description is largely sufficient for an agent to understand the tool's purpose. The main missing context is the origin of job_status_id and any polling semantics, but the simplicity keeps this from being a critical gap.

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%, so the description must compensate for the parameter's meaning. The name job_status_id and the tool description imply the parameter identifies the job, but the description never explicitly states that job_status_id is the ID returned when the background job was created, nor does it explain how to obtain or format it.

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 identifies the verb ('Get'), the resource ('status of a background job'), and gives a concrete example ('project copy'). The 'background job' qualifier distinguishes it from sibling tools like get_status, which likely operate on work package statuses rather than job status.

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 example 'such as project copy' implies it should be used to check on asynchronous background operations, which is useful but indirect. It provides no explicit guidance about when to poll, when not to use it, or how it relates to alternatives like get_status.

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