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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: default sort is newest-first, the response envelope is {count, results}, and it hits GET /jobs. It does not mention pagination ceilings (left to the schema), so it stops short of a 5.

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?

Two compact sentences plus a short return/endpoint note; the core purpose and ordering default are front-loaded and every clause conveys information. No filler or redundancy.

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 usefully discloses the return envelope {count, results} and the endpoint. Filter examples and default ordering are covered, though pagination limits and whether filtering is server-side versus client-side are left implicit.

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 100%, so every parameter is already documented in the schema (filter format, from/size semantics, sort defaults). The description restates the filter shape with one status example and explains what related_id does, but adds no syntax or constraints beyond the schema, landing at the baseline.

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 ('List jobs (projects)'), names the default ordering ('newest first'), and identifies the backing operation (GET /jobs). An agent can immediately distinguish this from jobnimbus_get_job (single record) or jobnimbus_create_job (write) without opening any schema.

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 explains how to filter ('by status ... or by the related contact via related_id'), which implies usage, but never states when to prefer this over sibling list tools (list_contacts, list_activities) or over jobnimbus_get_job. No explicit when-not guidance or prerequisites are given.

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