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

The description adds one useful behavioral trait: it creates a draft, implying the posting is not published yet. Annotations already convey that this is not read-only and not destructive, so the bar is lower, but the description does not disclose validation behavior, response shape, or side effects beyond creating the draft.

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 short, but it mostly restates the title, and 'through the public Yardstick API' is filler that provides no agent value. It front-loads the action but does not use its limited space to convey useful information beyond the title.

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 16-parameter create operation with no output schema and very low schema coverage, this one-sentence description is inadequate. It omits prerequisites, sequencing with interview plan publishing, idempotency behavior, and what the agent should expect after a successful call.

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 description coverage is only 13%, and the description says nothing about any of the 16 parameters. It does not compensate for the sparse schema by explaining required fields like slug, interview_plan_id, salary fields, or custom_questions structure.

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 action ('Create') and resource ('draft job posting'), and the 'draft' qualifier clearly distinguishes this create endpoint from publish, update, validate, or read siblings. The purpose is immediately understandable and unambiguous.

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?

No guidance is given about when to use this tool versus alternatives such as job_postings_update, job_postings_publish, or job_postings_validate. Prerequisites like needing a published interview plan already attached to a job are not mentioned in the description, and no exclusions or alternative routing are provided.

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