jobs_eightfold_job

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

No annotations provided, so description carries full burden. It usefully notes fallback behavior ('Tries the newer PCSX detail first, falling back to the legacy SmartApply detail generation') and that it's 'Credential-free public ATS JSON'. However, does not detail rate limits, response size, or any potential side effects.

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?

Three concise sentences: purpose, parameter guidance, behavioral notes. No fluff, front-loaded with the key action.

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?

Covers purpose, parameter sources, fallback behavior, and auth status. Lacks details on error handling or response format, but the tool is simple and the description is reasonable for its complexity.

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 description adds context: 'id is the position id from a board listing; tenant/domain as in the board endpoint' clarifies the source and usage of each parameter, going beyond the schema 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 'Get a single Eightfold position' and specifies it returns 'full HTML/text description'. Among siblings like 'jobs_eightfold_board' (listing) and other job-specific tools, this tool is uniquely for retrieving a single position 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?

Explains that 'id is the position id from a board listing; tenant/domain as in the board endpoint', implying prior knowledge from a board listing. However, does not explicitly state when to use this tool versus alternatives like 'jobs_eightfold_board' or other job detail tools.

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