jobs_icims_board

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

No annotations are provided, so the description carries full burden. It discloses that the tool is credential-free, public, returns JSON with full descriptions, paginated via page/limit, and clarifies the domain distinction. This is comprehensive behavioral information.

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?

Two sentences, front-loaded with purpose, no redundant information. Every sentence adds value: purpose, domain clarification, pagination, and public credential-free nature.

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 listing tool with 5 parameters and no output schema, the description covers purpose, parameters, pagination, and return format (jobs with full description inline). It could mention error handling or rate limits, but the schema's max 50 limit is sufficient. Overall, very 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. The description adds context for domain (careers domain vs employee portal) and implies pagination behavior, but does not add significant new semantics beyond the schema's parameter descriptions.

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 'List an iCIMS tenant's job board' and elaborates with specifics about the public nature, domain format, pagination, and inline descriptions. It distinguishes itself from sibling tools like jobs_icims_job by focusing on listing multiple jobs.

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 tells when to use this tool (to list public iCIMS jobs) and clarifies the domain parameter's meaning. It contrasts with the employee portal subdomain. However, it does not explicitly say when not to use it or mention alternatives among the many job board siblings.

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