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

The readOnlyHint annotation already establishes that this is a safe read operation, lowering the bar. The description adds that the tool returns both manual and cron jobs, which is mild behavioral context, but does not disclose pagination details, authentication requirements, or what happens when no jobs exist.

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?

A single efficient sentence that states the tool's purpose, the job type qualification, and the underlying endpoint. No filler or redundant phrasing.

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 straightforward list operation with full schema coverage and a readOnlyHint, the description is nearly complete. The absence of an output schema is acceptable since it is a list endpoint, though a brief note on pagination or that it returns an array might have made it fully self-contained.

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 the baseline is 3. The description's endpoint references {projectId}, which contextualizes that it is a path parameter, but it adds no meaning for page, cursor, or per_page beyond the schema.

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 operation ('List jobs') and the resource scope ('in a project'), and further specifies the job types ('manual / cron'). The explicit endpoint 'GET /v1/projects/{projectId}/jobs' and use of 'List' differentiate it from sibling get_job, making the purpose obvious.

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 context for when to use this tool is implied by 'List jobs' and the project scope, but there is no explicit guidance distinguishing it from alternatives like northflank_get_job or northflank_list_services. No exclusions or conditions are provided.

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