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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context by listing what the payload contains (full description, salary, language requirements, visa sponsorship, Ranked page URL, source freshness), which is otherwise unavailable since there is no output schema.

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 with the resource and lookup key front-loaded, followed by the field inventory. Nothing is wasted, though the long field enumeration makes it slightly list-like rather than crisply structured.

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?

Since there is no output schema, the description must describe the return payload and does so concretely enough for an agent to know what it will get. It omits only minor details like failure behavior for an unknown or expired id.

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 a single parameter and 100% schema coverage, the schema fully documents the id and even its provenance ('returned by search_jobs'). The description only restates 'by id' and adds no format, validation or edge-case meaning, so the 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 gives a specific verb and resource ('Full details of one Ranked job by id') and enumerates exactly which fields are returned, which is more than a restatement of the title. It implicitly separates itself from search_jobs by scoping to a single record, though it never names the sibling 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 only implied: 'by id' suggests it is the follow-up step after a search, and the schema notes the id comes from search_jobs, but the description itself states no when-to-use condition or alternative. Adequate but no explicit routing guidance.

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