nexus_list_jobs

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds behavior beyond annotations: it returns one page with a total count, and it may occasionally fail with transient server errors. This is useful operational context, though it does not cover auth or rate limits.

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 compact sentences, front-loaded with the core action. Each sentence adds value: function, filters, and error-handling guidance. No wasteful wording.

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 an output schema present and simple read-only behavior, the description sufficiently covers pagination, filtering, and error avoidance. It does not detail sort order or exact filter interaction, but these are not necessary for basic invocation.

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. It explains all four parameters: limit as page size, project as exact name, status with example values, and name_like as a substring. It does not explicitly describe null/default behavior or how filters combine, but the main semantics are clear.

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 clearly states the tool's purpose: list jobs visible to the user, with pagination details. It distinguishes itself from sibling tools like nexus_job_status and nexus_get_results by focusing on a list operation with filters rather than single-job operations.

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 explicitly provides when-not-to-use guidance and alternatives: in case of a Nexus-side server error, use nexus_job_status or nexus_get_results by id instead of retrying. It also mentions optional filters, which implies when to apply them.

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