freelance_create_job

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It strongly discloses the most critical behavioral trait: the posting is immediately visible to real people and can be bid on by freelancers, and it instructs agents to confirm details with a human before calling. It also states the organizational-token requirement. It does not cover failure modes, reversibility, or editability, but the most consequential side effect—public exposure—is well communicated.

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 three sentences, each earning its place: purpose and scope, the organizational prerequisite, and the safety warning with a specific visibility tip. The most important fact—immediate public visibility—is front-loaded and appropriately emphasized with capital letters. There is no fluff or repetition.

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?

The tool has a complex nested schema, but the schema itself documents the nested fields. The description fills the non-obvious contextual gaps: the organization-token requirement, the real-world visibility consequence, and the use of `visibility: ORGANIZATION` for internal work. It does not describe return values, but there is no output schema, so that is not required. It could mention cross-field dependencies (e.g., fixedBudget only with FIXED_PRICE), but those are already in the schema descriptions, so the description is sufficiently complete.

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 0% for the top-level 'input' parameter, so the description must compensate. It does for one key parameter: it explains the consequence of `visibility: ORGANIZATION` (keeping the job internal), which goes beyond the schema's simple enum listing. However, it adds no meaning for the many other nested fields, relying on their in-schema descriptions. This partial compensation warrants a 3.

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 action with a specific verb and resource: 'Publish a job posting to the marketplace under your organization's name.' It distinguishes the tool from the many read/search siblings in the list by emphasizing creation/publishing, and it also conveys the key organizational context—this tool operates on behalf of an organization, setting it apart from proposal/submission tools.

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 context and prerequisites: it belongs to the HIRE scope and requires an organization context on the token, explicitly noting that a personal token has nothing to post as. It also provides actionable guidance—confirm title, budget, and description with the user before calling, and use `visibility: ORGANIZATION` to keep the job internal. It does not name alternative tools, but no other sibling serves the same create-job purpose, so the context is sufficient.

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