get_job

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

With no annotations provided, the description carries the full burden. The verb 'Get' implies a read-only retrieval, and the description states that results include the full description. However, it does not explicitly confirm non-mutation, auth requirements, or any rate limiting; for a simple getter this is adequate but minimal.

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 compact and front-loaded with the primary purpose, followed by a clean two-argument breakdown. Every line provides useful information with no redundancy or filler.

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?

For a straightforward read tool with no output schema and no annotations, the description covers the core purpose and parameter semantics well. It does not describe the exact return shape beyond 'full details including its description,' but this is acceptable given the tool's low complexity.

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 description coverage is 0%, so the description must compensate, and it does. It explains job_board_name as the company slug from the URL pattern jobs.ashbyhq.com/{slug} and job_id as returned by list_jobs, adding essential provenance and format details absent from the bare schema titles.

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 uses a specific verb ('Get') and resource ('full details for one specific job posting') and explicitly notes the inclusion of the job description. This distinguishes it from sibling tools like list_jobs and get_latest_jobs, which target collections or recent postings.

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 parameter note that job_id is 'the job's id, as returned by list_jobs' establishes a clear workflow: call list_jobs first, then get_job for details. This provides clear context for when to use the tool, though it does not explicitly name alternatives or exclusion conditions.

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