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

The annotations already mark the tool `readOnlyHint: true`; the description adds substantial behavioral context: it requires the caller's API key, presents results newest-first, explains that `matched` jobs arrive via `job.matched` events or self-sent bids, and warns that titles/briefs live under `_untrusted` and are user-generated. This tells the agent about authentication and data-quality caveats well beyond the schema.

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 key idea ('Your side of the job board, needs API key, newest first') is front-loaded, and the two sublists are clearly delimited with backticks. However, the description is a dense single paragraph with long parentheses and clauses; it could be broken into bullet points and still be shorter. It is efficient but leans toward information overload, so a 4 is appropriate.

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?

With no output schema, the description must explain return shape, and it does most of it: `posted` jobs expose `status`, `matched_sellers`, `bids`, `paid_bids`; `matched` jobs include `my_bid` or null, and the `my_bid` object's key fields are listed. The `match` field and pagination details are not fully specified, but for a listing tool this is sufficient for an agent to call it and interpret results.

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?

Both `limit` and `status` are fully described in the schema (100% coverage), so the baseline is 3. The description adds only a restatement of filtering (`Filter with `status``) and 'newest first, per list' which repeats the schema's own phrasing; it does not clarify any ambiguity about whether `status` applies to both lists simultaneously, so no extra meaning is added.

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 opens with 'Your side of the job board' and defines two concrete sublists (`posted` and `matched`), making the resource and scope unmistakable. It distinguishes this from siblings like `searchJobs` and `getListing` by framing it as the user's personal job set and by explicitly naming follow-up tools (`getBids`, `closeJob`) that act on results. This is a specific, non-tautological description.

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?

It gives clear context for when to use the tool: any time you need your own posted or matched jobs. It goes further by pointing to `getBids(job_id)` and `closeJob` as next steps for handling `posted` jobs, helping the agent choose follow-up tools. It does not explicitly state negative conditions (e.g., 'use searchJobs for global search'), but the 'your side' framing implicitly excludes that, so the context is adequate.

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