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

With no annotations, the description carries the full burden and does add real value: result ordering (newest first), zero credit cost, the shape of each entry (status, attempts, credits, result or error), and a direct REST equivalent. It is silent on pagination/truncation behavior despite a limit parameter, and on the auth expectation behind api_key.

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 dense sentence with the account scope and ordering front-loaded, followed by the returned fields and the cost note. Every clause carries information; the telegraphic style is compact without being padded.

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?

An output schema exists, so the description need not explain return values, and the REST mapping plus 'Free' note cover the essentials. For a list tool with two undocumented parameters and unknown pagination semantics, however, the description stops short of what an agent needs to page through results reliably.

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% and there are two parameters, yet the description never mentions limit or api_key. The limit max of 100/default 50 and any pagination implication are left entirely unstated, so the description fails to compensate for the schema gap.

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 resource (this account's background jobs), scope (account-only), ordering (newest first), and concrete examples of job categories plus the fields returned. That is far more than a restatement of the name. It only implicitly separates itself from get_job / start_job (singular vs. plural, list vs. act) rather than naming the alternatives.

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?

Usage is implied by the enumeration of job types and the 'Free' note, which tells the agent the call costs no credits and is safe to poll. There is no explicit when-to-use/when-not or routing to siblings such as get_job for a single job's detail.

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