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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered. The description adds only the notion of a 'tenant', and does not disclose pagination behavior, rate limits, or what the board listing contains beyond the annotations.

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 fragment with no waste, but it is under-specified rather than efficiently concise. There is no front-loaded verb or scope detail to anchor the agent.

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 explained, but with 5 undocumented params, no usage guidance, and no differentiation from the jobs_icims_job sibling, the description is too thin for a paginated board-listing tool.

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% across 5 parameters, so the description must compensate and largely does not. It only loosely hints at the required 'domain' via 'tenant' and says nothing about page, limit, keywords, or location, leaving four parameters undocumented anywhere.

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 phrase 'iCIMS job board listing for a tenant' names the resource (an iCIMS job board) and implies a listing/retrieval action, which distinguishes it from the singular jobs_icims_job sibling. However, there is no explicit verb and no direct comparison to the sibling, so an agent must infer that this returns a collection rather than one posting.

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 alternatives like jobs_icims_job or jobs_company_search, nor any stated prerequisites beyond the implied tenant. The agent gets no when/when-not signal.

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