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

Annotations already cover read-only/idempotent safety, and the description adds value beyond them: the personal-access-token requirement, the newest-first ordering, and precise semantics for each status value including the prohibition on conflating unconfirmed/sent with submitted. That is exactly the behavioral context an agent cannot derive from structured fields.

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 purpose in the first clause and then spends words only on the status/outcome distinctions, which carry real disambiguation value. Slightly dense with repeated 'never call X submitted' phrasing that could be tightened, but nothing is wasted.

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?

Output schema exists so return shape needn't be explained, and the description still supplies the semantic meanings of status and outcome codes plus auth needs. The only gap is the absence of any pointer to list_auto_apply_queue for the queue-vs-history distinction.

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% and the limit parameter (1-25, default 10) is fully documented there. The description adds nothing about limit, so the baseline of 3 applies.

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 (jobs the extension worked on for the user) plus the ordering (newest first) and the fields returned (status, source, outcome). It doesn't explicitly contrast with list_auto_apply_queue, so an agent must infer that this is history versus pending queue.

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 only implied by 'the jobs the extension worked on' – past tense suggests completed attempts rather than queued ones. No explicit when-to-use or when-not-to-use, and no sibling tool is named even though list_auto_apply_queue is the obvious alternative.

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