job_details

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

No annotations are provided, so the description carries the burden. It accurately describes a read operation ('Get') with no side effects, but does not disclose prerequisites, auth requirements, or performance implications like batching/quota, which are documented in the schema. The description is honest but adds minimal behavioral context.

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?

Single sentence, front-loaded with the main action, and no fluff. It efficiently conveys the scope and examples without unnecessary detail.

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?

Although there is no output schema, the description provides a reasonable overview of return content, including specific additional info. The schema documents all parameters, so the description is sufficiently complete for an agent to invoke the tool, though it doesn't mention batching or field projection explicitly (those are in the schema).

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 coverage is 100%, with detailed descriptions for each parameter (batching, allowed values, defaults). The description adds no parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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?

Description uses specific verb 'Get' and resource 'all job details', listing concrete additional info (application options, employer reviews, estimated salaries). This clearly distinguishes it from siblings like job_search and job_salary, which focus on searching and salary-specific data.

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?

The description implies use for retrieving comprehensive details for a specific job but does not explicitly mention alternatives or provide when-not-to-use guidance. It is clear enough for an agent to know this is for detail lookup, but lacks explicit exclusions.

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