jobs_rippling_board

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

Description mentions 'Credential-free public ATS JSON', indicating no authentication needed. Discloses that it returns thin listings. No annotations provided, so description carries full burden. Lacks pagination or rate limit info but sufficient for basic behavioral understanding.

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?

Four sentences, each adding value: purpose, data scope, URL format, and credential requirements. Efficiently front-loaded.

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?

Covers purpose, data content, URL format, and authentication. Could mention pagination or result limits, but for a simple listing tool the description is nearly complete.

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%, so baseline is 3. Description adds context for the company parameter by specifying the exact URL format (https://ats.rippling.com/{company}/jobs), enriching schema description. Other parameters are well-described in 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?

Description clearly states the tool lists a company's Rippling job board postings, specifying the data included (title, department, work location) and differentiating from the detail endpoint. Distinguishes from sibling tool jobs_rippling_job.

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?

Description implicitly guides use by indicating this tool provides thin listings and points to a separate endpoint for full details. However, it lacks explicit when-to-use vs alternative job board tools (e.g., Ashby, Greenhouse).

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