List job postings

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'List' clearly indicates a read operation, and the filter behavior is explicit, but the description does not address pagination, ordering, return format, or permission requirements. It is adequate but not richly transparent.

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?

A single, front-loaded sentence states the action, the resource, and the one parameter nuance. There is no wasted wording, and the optional filter is placed exactly where it is useful.

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 low-complexity tool with one optional boolean parameter, no required parameters, and no output schema, the description is largely complete. It omits non-essential details like return shape or pagination, which are not necessary for an agent to select and invoke the tool correctly.

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%, but the description compensates by explaining the 'published-only' filter, which maps directly to the published_only boolean parameter. It makes the parameter's optionality clear, and the schema's default of false is consistent with 'optionally filtered.'

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 action ('List') and a specific resource ('career/job postings'), which clearly distinguishes it from sibling tools like create_job_posting, update_job_posting, and list_job_applications. The optional published-only filter adds further precision to what the tool returns.

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 gives clear context for use: call this tool when you need job postings and optionally want to restrict results to published ones. It does not explicitly name alternative tools or exclusions, but the intended use case is obvious for a simple read-only list.

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