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

The description discloses the immediate $2 posting fee, the requirement of a saved payment method, and ties the action to the 'Post a Job' form. The annotations provide destructiveHint=true, but the description adds the critical financial consequence. This is significant behavioral disclosure beyond what annotations or schema convey, and it doesn't contradict anything in the annotations.

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?

Two sentences, both informative. The first sentence states the action and equivalent form, the second communicates pricing and payment behavior. There's no fluff; every word adds value.

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 combination of schema (which documents all parameters and idempotency) and the description's disclosure of the fee makes it complete. It doesn't describe what the response containseding, but with no output schema and an uncomplicated job-posting flow, this is a minor gap. It might be worth mentioning that a saved payment method is required, which the description does mention. Slightly incomplete on post-conditions/response shape, hence 4.

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 100%, so the schema already documents all parameters well, including the idempotency_key semantics denouncing double-charging risk. The description adds no new parameter-specific details beyond what is in the schema. Baseline 3 is appropriate.

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?

Description states a specific verb and resource ('Post a new job listing'), clarifies it acts on behalf of the authenticated user, and explicitly equates it to the website's 'Post a Job' form. This distinguishes it clearly from siblings like cancel_job, complete_job, and browse_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?

The description gives context by referencing the website form, which implies when to use it. However, it does not explicitly state when not to use it or mention alternatives (e.g., submitting a bid via submit_bid). The fee and payment requirement imply a use case but no explicit routing guidance is given. Clear context, but lacks exclusions or alternatives.

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