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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that bonus amounts are quoted verbatim from the posting and that the full posting text is returned, which is useful context, but it omits error behavior for invalid/missing identifiers despite requiring zero parameters.

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?

It is a single front-loaded sentence that leads with the primary payload ('The whole posting text from the employer') before enumerating secondary fields. It is somewhat run-on and list-like, but every item arguably describes returned content and no sentence is wasted.

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 thoroughly, enumerating posting text, requirement facts, pay, bonus, benefits, open status, and apply link. The main gap is that it never resolves which identifier (url vs job_id) to supply, or what happens if neither is given.

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?

With only 50% schema coverage, the description must compensate for the undocumented url parameter, but it says nothing about either input. It states that an apply link is returned, which actually adds confusion about whether 'url' is the same link. The description describes output fields rather than adding meaning to the two parameters.

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 title states a specific verb+resource (read one job posting in full) and the description enumerates exactly what that posting contains, so the agent knows what it retrieves. It does not, however, distinguish itself from siblings like is_job_still_open (which it partially overlaps by including 'whether it is still open') or search_live_jobs.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives. The overlap with Sibling is_job_still_open is never addressed, so the agent must infer whether to call that tool separately or rely on the open-status field here.

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