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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds useful behavioral context beyond that: it enumerates what is returned per job and per account and explicitly states that finished jobs are excluded. Missing only edge details like pagination or auth scope.

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?

Front-loads the action and scope in the first clause before adding return-field detail, then closes with the exclusion and the alternative. Two dense sentences with no filler.

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 compensates by enumerating returned fields (jobid, type, start time, artifact, account health, maxJobs, running count, usage). It is complete enough to call correctly, though a note on result size or pagination would round it out.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline for a 0-param tool is 4, and the description correctly implies the endpoint takes no filtering arguments (GET /jobs).

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 (List) and resource (jobs) with explicit scope: jobs the token is running now, grouped per account. It enumerates the returned fields and names the sibling for the excluded case (finished jobs → notebook_get_job), so an agent can distinguish it from neighbors without opening a 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?

Clearly scopes usage to currently-running jobs and routes finished-job reads to notebook_get_job with a condition. However, it does not address potential overlap with notebook_get_account, which also exposes account health/maxJobs/usage fields, so one sibling overlap is left unaddressed.

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