jobs_oracle_board

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

With no annotations provided, the description carries full disclosure burden. It states the tool is credential-free, returns public data, and is paged. It mentions the listing includes a short description, but does not elaborate on rate limits or response format structure.

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?

The description is three sentences long, each sentence adds unique and necessary information. No wasted words; the most critical details (purpose, parameters, access, alternative) are front-loaded.

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?

Without an output schema, the description provides a reasonable overview: returns a paged listing with short descriptions. It could be more specific about response fields or error scenarios, but the core behavior is sufficiently covered for an agent to select and use the 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 coverage is 100%, but the description adds valuable context beyond parameter names: it explains how host and site are derived from the careers URL, and notes that limit/offset control paging. The search parameter semantics are left to the schema.

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 the action (List), the resource (Oracle Recruiting tenant's job board), and key features (paged via limit/offset, credential-free). It differentiates from the sibling jobs_oracle_job by noting the single-job endpoint provides full detail.

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 explicitly says to use the single-job endpoint for full detail, providing clear guidance on when to use an alternative. It also establishes context (public, credential-free) that helps determine appropriateness.

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