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 adds the useful behavioral detail that the returned job includes its home address, but it says nothing about read-only behavior, permissions, error handling when the job is not found, or what else is returned.

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 very short and front-loaded, with no wasted sentences. However, it is so terse that it reads as under-specified rather than optimally concise.

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 output schema exists, so return values need not be fully documented. Still, for a tool with no annotations and an undocumented required input parameter, the description is not complete enough to guide reliable invocation.

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?

There is one required parameter, job_id, with 0% schema description coverage, and the description does not mention it at all. It does not explain the identifier format, source, or whether it is the internal job ID.

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 conveys that this retrieves a single job and explicitly notes it includes the home address. However, it lacks an explicit retrieval verb and does not distinguish itself from siblings such as jobs_list or jobs_findByTag beyond the singular 'one job'.

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 given about when to use jobs_get versus jobs_list, jobs_findByTag, or other job-related tools. The singular wording implies single-record lookup, but no alternatives or exclusions are stated.

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