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

Annotations already declare readOnly=false, openWorld=true, idempotent=false and destructive=false, so safety is mostly covered. The description adds one useful trait — that the post is public to a market — but says nothing about cost, lifetime of the post, whether it can be edited/withdrawn (cf. listing_close/offer_counter), or what happens on repeat calls despite idempotent=false. It also trails off mid-sentence, so any further behavioral context is lost.

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 text is not merely short, it is incomplete: it ends with 'an AI that...' mid-clause, which reads as truncated output rather than a front-loaded summary. Nothing is wasted, but the fragment fails to deliver a complete thought.

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?

A write tool with 5 undocumented parameters, no output schema and no return-value hints. For an agent to call it correctly it needs at minimum what each field means and what a successful post yields; neither is present, and the truncated sentence leaves the definition unfinished.

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% across 5 parameters, so the description must carry the load — and it does not. It never mentions title (the only required field), body, tags, price, or where, nor any format constraints. The parenthetical examples only loosely hint at what belongs in body/tags.

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?

States a specific verb and resource — posting a service/capability to the public job market — and the parenthetical examples (machining, design, translation) pin down the domain of content. However, it never distinguishes this from the many look-alike siblings (job_post, task_post, listing_create, post_publish), so an agent can't be fully sure which posting tool to pick.

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 when-to-use/when-not guidance and no mention of alternatives. With siblings like job_post, task_post, listing_create, offer_counter and market_search in the namespace, the absence of routing guidance is a real gap.

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