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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety bar is low. The description adds one useful behavioral note (flop-devnet jobs appear when posted) and the title scopes it to test/devnet, but it says nothing about result ordering, limits, or pagination.

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?

Three short, front-loaded sentences with no filler; the core list action and optional filter come first. It is efficient, though the terse phrasing leaves a little to be desired in flow.

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 simple read-only list tool with a single fully documented optional parameter and no output schema, the definition is adequate. It omits any indication of what a returned job looks like or whether results are bounded, which an agent might want before relying on it.

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 100% with a well-described single optional parameter, so the schema already carries the semantics. "Optional mint filter" merely restates the mint param without adding format, matching behavior, or edge-case guidance.

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 open/funded campaign jobs") that clearly separates it from mutation siblings like crew_job_create, crew_job_fund, and crew_job_payout. No sibling is named for contrast, but the read-oriented listing purpose is unambiguous.

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?

Implies the use case (fetch open/funded jobs, optionally narrowed by mint) and the title flags it as test/devnet only. However, it never states when to prefer this over a discovery sibling such as crew_discover, nor any exclusion conditions, leaving routing to inference.

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