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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by enumerating the status code semantics (Processing -1, Completed 0, Error 1, Cancelled 2) and noting that Oracle's details text is returned, which helps an agent interpret results.

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 sentences, front-loaded with the return-value semantics followed by the usage context. No filler, every clause carries information an agent needs.

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?

With no output schema, the description carries the burden of describing return values, and it does so reasonably by listing status codes and the details text. It lacks guidance on polling cadence or whether status is eventually consistent, which is a minor gap for a status-check tool with full safety annotations.

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 coverage is 100%, with jobId, appName, and connection all documented in the schema itself, including defaults. The description only implicitly references jobId via 'a job in the connected application' and adds no format or syntax detail beyond the schema, so baseline 3 is appropriate.

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?

Names a specific verb and resource ('Returns the status of a job') and enumerates the exact status codes with their numeric values. This distinguishes it cleanly from sibling tools like run_business_rule, which it explicitly cross-references.

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 says when to invoke it ('Use it after run_business_rule or any job submission to see whether the job finished'), which is a clear usage trigger. It stops short of stating exclusions or naming alternative polling/status mechanisms, so it is not a full 5.

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