create_job

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

With no annotations, the description indicates a create operation via POST. It does not disclose potential side effects, permissions needed, or idempotency. The description remains adequate but lacks depth on behavioral traits beyond creation.

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 and well-structured: a brief endpoint statement, a list of required fields, enum code explanations, and references to sibling tools. Every sentence provides essential information 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 18 parameters, the description covers the seven required ones and explains enums and custom_fields. It does not detail optional parameters like city or salary, but the schema indicates they are nullable. The presence of an output schema reduces need for return value explanation. Overall, it is sufficiently complete for a creation 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 0%, so the description adds significant value by listing the seven required fields, explaining enum meanings for job_status and job_location_type, and describing the format of custom_fields. This compensates for the lack of schema documentation.

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 'Create a job requisition via POST /v1/jobs.' It specifies the endpoint and lists all required fields, distinguishing it from siblings like update_job or list_jobs.

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 explicitly lists seven required fields and provides enum codes for job_status and job_location_type. It also directs users to use list_hiring_pipelines and list_job_custom_fields for related IDs. However, it does not mention when not to use this tool or alternatives.

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