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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the phrase 'with full description', which hints at a complete record but discloses nothing about auth requirements, whether the company identifier is a slug or domain, or rate/coverage limits for the Rippling source.

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 short sentence with no filler and the key qualifier front-loaded, which is structurally fine. However it is terse to the point of under-specification rather than genuinely concise, packing no actionable detail into its brevity.

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?

An output schema exists so return values need not be described, and annotations cover the read-only nature, but for a two-parameter lookup with zero parameter documentation the description is incomplete: it explains neither how to identify a job nor when this tool is the right one to call.

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% for both required parameters, so the schema supplies only names and types. The description never mentions 'id' or 'company' and gives no format, example, or note that 'company' is a Rippling tenant identifier paired with the job id, leaving the agent to guess how to construct a valid call.

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 names a concrete resource ('Rippling job') and qualifies it with 'Single ... with full description', which distinguishes a detail lookup from the sibling listing tool jobs_rippling_board. It is a sentence fragment without a verb, so the retrieve action is inferred rather than stated, but the resource and scope are unambiguous.

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?

There is no guidance on when to use this tool versus jobs_rippling_board or the other per-ATS job detail tools (jobs_greenhouse_job, jobs_lever_posting, jobs_workday_job, etc.). The agent must infer that this is the drill-down for a job surfaced elsewhere, and nothing states prerequisites or the identifier's provenance.

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