list_archived_tasks

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

No annotations are provided, so the description carries the full burden. It mentions optional filtering but does not disclose other behaviors such as default ordering, pagination, or what happens if no tasks match. For a read operation, the description is adequate but lacks some details.

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 a single sentence that is efficient and front-loaded. It clearly states the main action and context. However, the inaccuracy about date filtering slightly detracts from its conciseness value.

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 the tool's simplicity (2 optional parameters, no output schema), the description covers the core functionality. It lacks details on ordering, pagination behavior, and the absence of a date parameter is confusing. It is minimally adequate.

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 input schema has 100% description coverage, so baseline is 3. However, the description claims filtering by date, which is not a parameter, creating a contradiction. This inaccuracy reduces the score, as it does not add meaning and may mislead.

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 states the action (lists tasks), the resource (archive/ directory), and the context (completed work history). It distinguishes from siblings like 'list_tasks' and 'archive_task'. However, it mentions optional filtering by date, but the input schema does not include a date parameter, which is a minor inaccuracy.

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 usage for viewing completed work history, suggesting it is for archived tasks rather than active ones. However, there is no explicit guidance on when to use this tool versus alternatives like 'list_tasks' or 'search_tasks', nor any when-not-to-use conditions.

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