jobs_oracle_job

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

No annotations are provided. The description notes that the tool is 'credential-free', indicating no authentication is needed. It does not disclose rate limits or other constraints, but for a read-only public API, it is sufficiently transparent.

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 two sentences, front-loaded with the core purpose. Every sentence provides essential information without redundancy. It is efficient and clear.

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 simple retrieval tool with no output schema, the description adequately conveys what is returned (full description with fields), how to get the id (from a board listing), and that it is credential-free. No critical information is missing.

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?

The input schema has 100% coverage for all three parameters. The description adds context by linking id to a board listing and host/site to the board endpoint, reinforcing the schema descriptions and adding value.

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 tool retrieves a single Oracle Recruiting requisition and specifies the returned content (full HTML/text description with description, responsibilities, qualifications). It distinguishes from sibling tools like jobs_oracle_board by focusing on a single item.

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 explains that the id comes from a board listing and host/site are as in the board endpoint, providing context for use. However, it does not explicitly mention when not to use this tool or name alternatives, though the sibling list includes many job tools.

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