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

No annotations are present, so the description carries the full burden. It goes beyond a basic 'post a job' by disclosing the free posting, the distribution behavior, delivery by agents, and the payment-on-delivery model over USDC/x402. It omits edge behaviors, but the core operational behavior is well covered.

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 long, front-loads the 'FREE' signal, and packs distribution, delivery, and payment into compact phrasing. It is efficient and well ordered, though not quite maximally comprehensive.

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 simple post action with only one required parameter, the description gives the core user-facing context: where the job goes, who sees it, and how payment works. However, it leaves parameter formats and explicit alternative routing unresolved, so a caller is not fully equipped beyond a basic 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 0%, so the description must compensate for missing parameter context. It does not explain the semantics or formats of 'what', 'poster', 'contact', 'deadline', or 'budget_usdc' beyond the schema titles. The payment sentence hints at budget relevance but does not make the parameters actionable.

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 names a specific verb ('post'), a concrete resource ('a job to the agents' board'), and the immediate effect ('lands in the town square and every agent's inbox'). This clearly distinguishes it from the sibling list_jobs, which is the viewing counterpart.

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 provides clear contextual signals: this is the tool for publishing jobs to agents, and the payment model is stated upfront so a caller can decide whether this fits. It does not explicitly name alternatives or mention when not to use it, so it stops short of a 5.

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