Create JobZyn job

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

Beyond the annotations, the description reveals key write behavior: immediate publication by default, the UNPUBLISHED draft path, 409 on duplicate external IDs, and preservation of additional fields. This is substantial behavioral disclosure for annotations that only provide generic hints.

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 compact and front-loaded: endpoint and scope first, then requirements and behavior. Every sentence earns its place by stating a requirement or a behavioral consequence.

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 creation tool with no output schema, te description covers endpooint, required subfields, default status, draft option, duplicate behavior, and open-world field handling. It omits the response shape, but an agent has enough to invoke the tool correctly and understand common failures.

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 top-level job parameter has no schema description, so the description compensates by identifying required id/title subfields and adding status and duplicate-ID semantics. It does not enumerate every optional field, but the nested schema already documents those details.

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 states a specific verb and resource: 'Create a job (POST /job, write scope).' It also clarifies required fields and creation defaults, which clearly distinguishes it from siblings like jobzyn_update_job or jobzyn_get_candidates.

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 gives clear usage context: job.id and job.title are required, and the caller must choose between PUBLISHED (immediate public) and UNPUBLISHED (draft). It does not explicitly name update_job as the alternative for existing IDs, but the duplicate-external-ID 409 behavior implies the boundary.

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