Get full details for a specific job listing including description, requirements, salary, and apply link. Use the job_handle ID from search_jobs results.
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes | Job handle from search results (e.g. "dropbox-senior-full-stack-software-engineer-d3f1k") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds the scope of returned details and the expected input source, but it doesn't describe edge cases like invalid job IDs or partial results. The additional behavioral context is modest but non-zero.
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 two compact, information-dense sentences. The first sentence immediately states the purpose and expected output content, and the second gives the input provenance without unnecessary prose.
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 simple single-parameter read tool with annotations and full schema coverage, the description is nearly complete: it indicates the input source, the output scope, and the operation type. It could add a tiny bit more about error handling, but nothing critical is missing.
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?
The input schema already describes job_id as 'Job handle from search results (e.g. ...)', which is essentially the same content the description repeats via 'Use the job_handle ID from search_jobs results.' With 100% schema coverage, the description does not meaningfully extend parameter understanding.
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 states a specific verb ('Get'), a specific resource ('specific job listing'), and the scope ('full details ... including description, requirements, salary, and apply link'). It also implicitly distinguishes itself from siblings like search_jobs by focusing on a single listing.
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 clearly indicates that job_handle IDs originate from search_jobs results, which tells an agent how to obtain the correct input. It does not explicitly list exclusions or when not to use it, but the usage context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: search finds jobs, get_job retrieves details, find_similar_jobs does similarity matching, get_company looks up employer info, and get_filter_options provides search metadata. There is no meaningful overlap or ambiguity.
All tools follow a consistent snake_case verb_noun pattern (search_jobs, get_job, get_company, get_filter_options, find_similar_jobs). The verbs are varied but semantically appropriate, and there are no mixed conventions.
Five tools is a well-scoped set for a job search and discovery data lake. Each tool covers a necessary step in the workflow without redundancy or excessive surface area.
The toolset covers the full read-only job discovery workflow: filtering/searching, accessing full job details, finding related jobs, and retrieving company information. There are no obvious dead ends or missing operations for the stated purpose.