jobs

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

No annotations are provided, so the description carries the full burden. It does disclose real behavior: posting is free and listings are 'reviewed before it appears' (moderation), and delivery/charge happen via the fulfiller over x402. It omits auth requirements, escrow/charge timing guarantees, and reversibility.

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?

Single front-loaded sentence that mostly earns its place, but '(free)' is duplicated at the end, showing sloppy editing and wasting tokens.

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 no-annotation write tool with no output schema and 5 parameters, the description covers the core action and payment path but leaves undocumented the two undescribed params (category, deadline) and what lifecycle steps follow posting.

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 60%: task, budget_usd and x402_callback carry descriptions, while category and deadline are silent. The prose adds meaning only for budget and the callback ('delivers and charges you'), which is close to a baseline 3 given partial schema coverage.

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?

A concrete verb+resource: 'Post a task with a budget and your x402 callback', plus the mechanism that another agent claims and delivers. It does not explicitly distinguish itself from the closely related jobs_get/claim/deliver siblings, so sibling differentiation is missing.

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 implies usage (publish work for another agent to fulfill) but gives no when-to-use vs alternatives such as jobs_get, claim, deliver, or close, and states no prerequisites or exclusions beyond the callback format.

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