Get Job Listing

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the response includes selection panel, custom application form definition, scorecard, pipeline stages, and full text/web content, providing useful context about what to expect from the call.

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 tight sentences: the first packs purpose and return details, the second offers a pointer to list_jobs. No redundant words.

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 single-parameter get tool with no output schema, the description is remarkably complete: it specifies the input format, the scope (single listing), and enumerates the major response components. It also tells the user how to obtain the 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?

The schema already fully documents job_id as 'The unique job listing ID or slug' (100% coverage). The description adds a concrete example ('forklift-driver-oz0H') and reinforces the slug format, adding value beyond the schema.

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 clearly states 'Get a single job listing by its unique job ID/slug' with a specific verb (Get) and resource (job listing). It also lists key fields included (selection panel, scorecard, etc.), distinguishing it from sibling list_jobs and other get_* tools.

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 explicitly names list_jobs as the way to find job IDs, providing a clear pointer to an alternative. It implies this tool is for single job retrieval when full details are needed, though it doesn't explicitly state when not to use it.

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