indeed_job: GET /

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

As a read operation, it is safe, but the description does not explicitly state idempotency or lack of side effects, relying on the 'Fetches' verb to imply a read.

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 concise, front-loaded with the purpose, and uses bullet-like listing of use cases without redundancy.

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?

Given no output schema, the description lists many expected fields, making it fairly complete for typical use, though it doesn't mention optionality or format.

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 description adds context that the URL is a 'viewjob URL,' beyond the schema's generic 'URL of the job vacancy,' and with 100% schema coverage, it adds 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 fetches a single Indeed job posting by its viewjob URL and lists the returned fields, distinguishing it from sibling listing tool.

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?

It suggests use cases like ATS/CRM enrichment and mentions using it after the Indeed Listing endpoint, implying when to use, though not explicitly stating when not to.

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