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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful non-annotation context by disclosing that the response includes user-specific state (saved/applied/stage/note), which signals a personalized read. It says nothing about behavior for a missing or invalid job_id, nor about any per-user auth requirement.

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?

One dense sentence, front-loaded with the core fact (one job, in full) followed by the returned fields. No filler, no repetition of the title, and every clause contributes information.

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 return-value burden and does so well by enumerating the fields an agent will get. For a simple one-parameter read the definition is nearly complete; the only omission is error/not-found behavior and confirmation that the id must originate from a list call.

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 a single parameter with 100% schema description coverage ('A job id from any list'), so the schema carries the semantics. The description's 'one job in full' only reinforces that job_id selects the record; it adds no format, source, or validity detail beyond the schema. 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?

The description names the resource (one job) and enumerates exactly what comes back — description, summary, skills, years, places, hiring system, apply link, plus the user's own status. That distinguishes it from list-oriented siblings like search_jobs, my_jobs, or company_jobs. It lacks an explicit verb ('retrieve'/'fetch') and never names a sibling directly, so it stops short of a 5.

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 only implied: an agent can infer this is the tool for full detail on a single job after a list/search returns an id. There is no explicit when-to-use statement, no exclusion of alternatives (e.g., similar_jobs or company_jobs for related items), and no note about what to do if the id is unknown.

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