get_job_status

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It states the tool 'Get[s]' something, implying read-only, but does not mention permissions, side effects, rate limits, or any caveats about job availability. The description adds little beyond the basic purpose.

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 no wasted words. It is front-loaded with the verb and resource, and the example adds context without verbose elaboration.

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?

The tool is simple (get by ID) and an output schema exists, so return values are covered. However, the description lacks context on how to obtain a job_status_id or when this tool fits into a workflow. It is minimally viable but leaves the agent without enough context for complex decision-making.

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%, and the description barely explains the single parameter 'job_status_id'. It gives an example ('such as project copy') but does not clarify what the ID represents, where it comes from, or how it relates to the job. The description does not meaningfully compensate for the lack of schema documentation.

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 a specific verb (Get) and resource (current status of a background job), with an illustrative example ('such as project copy'). It distinguishes itself from all sibling tools, which focus on different entities like sprints, documents, or work packages.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of how it relates to other tools that might trigger background jobs. The description implies its use for checking job status but does not provide context such as 'use after starting a job' or alternatives.

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