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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), but the description adds real behavioral context: credential-free public ATS JSON (no auth), full description returned inline per job, and the warning that the bare subdomain is OAuth-gated. That access/return context goes beyond what the annotations state.

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?

Purpose is front-loaded in the first clause, and the domain caveat is placed where it matters. The em-dash parenthetical and multiple nested asides make the single long sentence slightly dense, but no sentence is filler.

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?

With an output schema present, return-value explanation is not needed, and the description still flags that full descriptions come inline. For a domain-ambiguous multi-page listing tool it covers the critical operational details (correct domain, paging, credential-free access), leaving only broader sibling routing unaddressed.

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 the schema already documents all five parameters. The description reinforces the domain semantics (the tenant's careers domain from its careers URL) and notes page/limit paging, but adds little syntax or format detail beyond the schema — the baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (Lists) and resource (a company's public iCIMS job board), and immediately disambiguates the target — the white-labeled careers domain, not the {company}.icims.com subdomain. An agent can distinguish it from jobs_icims_job (single job) without reading either schema.

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?

Names the sibling alternative explicitly ('Use jobs_icims_job to get a single iCIMS job') and supplies a concrete when-not condition for the domain (avoid the OAuth-gated employee subdomain). It stops short of contrasting with the broader job-board siblings (jobs_company_search, jobs_workday_board, etc.), so it is clear but not exhaustive.

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