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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful context that the response covers build/deploy config and cron schedule, but says nothing about auth, error behavior for missing jobs, or response shape beyond that summary.

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 tight sentences with the core purpose front-loaded and no filler; the endpoint is appended as supporting detail rather than padding.

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 two-param read-only fetch with full schema coverage and readOnlyHint, the description is nearly complete; calling out the returned fields partially compensates for the missing output schema. Only error/not-found behavior is unaddressed.

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% and the schema already ties jobId back to northflank_list_jobs. The description adds no parameter-level meaning beyond the REST path template GET /v1/projects/{projectId}/jobs/{jobId}, which merely restates the two required params. 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 and resource ('Get details of a single job') and enumerates the payload contents (build/deploy config, cron schedule). It implicitly contrasts with northflank_list_jobs via 'single job', but never names the alternative explicitly.

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: fetch details for one job once you have a jobId, as referenced by the parameter description. There is no explicit when-to-use versus northflank_list_jobs or when-not guidance, nor any note about prerequisites.

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