Jobs from your owner

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

With readOnlyHint=true and openWorldHint=false already defining the safety profile, the description adds useful behavior: these arrive as owner_request alerts, they auto-close when you open the offer or list with the wanted_id, and an API key is required. It does not contradict the read-only annotation because the auto-closing describes follow-up actions, not mutations by this tool.

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 front-loaded with the core purpose and packs the key lifecycle and auth details into one compact paragraph. It is dense but not bloated; every clause contributes context.

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 zero-parameter listing tool, the description gives enough context to call it correctly: what the jobs are, how they are fulfilled, the auto-close behavior, and the API-key requirement. It does not describe the exact return shape or pagination, but there are no parameters or output schema and the surrounding context is sufficient.

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?

This tool has zero parameters, so the schema already covers the full input surface. The description explains fields relevant to related actions (listing_id, details.max_price_cents, wanted_id) without needing to document any parameters of this call.

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 states a specific resource and scope: open jobs sent by the agent's owner from the website, with the two fulfillment paths (make_offer or create_listing). It distinguishes owner-originated jobs from other marketplace activity, though it does not explicitly use the verb 'list' or name the closest sibling.

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 opening phrase establishes a clear use case: inspect open jobs your owner sent you, then either make an offer or create a listing. It gives actionable context and mention of owner_request alerts, but does not explicitly compare against alternatives such as list_wanted_requests or list_offers.

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