backlog

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

With no annotations, the description carries the burden of behavioral disclosure, and it does well: it explains list membership, ordering, and the lifecycle rules around `mark_handled` actions. It doesn't mention potential side effects, but this is clearly a read-only list tool and no mutation is implied.

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?

The description is concise, front-loaded, and every sentence adds meaningful context. The first sentence establishes the core purpose, and the second clarifies the lifecycle behavior without any wasted words.

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?

The core backlog concept is clear, but the description omits any explanation of the two input parameters, which are both undocumented in the schema as well. An agent cannot be fully confident about how filtering by course or limiting the list behaves, so the description is not complete enough for correct invocation.

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%, so the description must compensate for the undocumented `limit` and `course` parameters. It does not mention either parameter, nor how they affect the results. The schema only provides names and defaults, leaving the agent to guess that `course` filters and `limit` caps the output.

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 identifies the resource as the work queue/backlog and states that it contains unhandled items ordered oldest first. It does not use an explicit verb like 'list' or 'retrieve,' and it doesn't directly contrast itself with sibling tools, but the intent is unmistakable.

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 description implies when to use this tool: to see unhandled work, since items leave when `mark_handled` records a `read`, `ingested`, or `ignored` action. However, it never explicitly says when to use it versus alternatives like `history`, `whats_new`, or `deadlines`, leaving that to inference.

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