list_tasks

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

Annotations already indicate idempotent read-only behavior. Description adds that it returns one page and defaults to unacknowledged, providing useful behavioral context beyond annotations.

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?

Two crisp sentences, no redundancy. Front-loads the main purpose, then adds key behavioral details. Every part earns its place.

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?

Given an output schema, return value details are handled. However, not all parameters are explained, and the description's brevity leaves out filtering nuances that would aid full understanding.

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?

With 0% schema coverage, description partially compensates by explaining the role of 'include_acknowledged' and 'acknowledged' parameters. However, it omits semantics for 'page', 'page_size', and 'status', leaving gaps.

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?

Clearly states it lists 'Paperless Celery tasks', specifying the resource. Distinguishes from get_task (single task) but not from other list tools in siblings, though context makes it clear.

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?

Describes default behavior (unacknowledged) and how to see acknowledged tasks, implying usage context. However, no explicit guidance on when to use vs alternatives like wait_for_task or get_task.

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