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

Adds real context beyond the readOnly/openWorld annotations: credential-free public access, that postings carry only a brief inline description, and that the full detail page is HTML rather than JSON. These are non-obvious behavioral facts an agent needs. Does not cover rate limits or exact page-size behavior, so not a 5.

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?

Front-loads purpose, then sourcing, then caveats, then the sibling pointer. Every sentence carries information; slightly dense but no 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 values need not be described, and the description still covers the inline-description behavior. A credential-free, paged, public ATS list tool is fully specified for correct invocation.

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 baseline is 3, but the description adds meaningful semantics: the URL template https://recruiting.ultipro.com/{tenant}/JobBoard/{board} shows where both required values are sourced, which the schema only gestures at ('careers URL'). Genuine added value over the schema text.

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 and resource ('Lists a UKG Pro Recruiting tenant's public opportunities') with paging semantics, and explicitly distinguishes itself from the sibling datasets_jobs_search by scope. An agent can route between the two without opening 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 alternative (datasets_jobs_search) along with the condition that selects it – searching all companies' live postings versus this tenant's board. The implied 'when' is explicit enough to route correctly.

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