get-tasks-list

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

Annotations already establish readOnlyHint, destructiveHint false, and openWorldHint false, so the safety profile is covered. The description adds default filtering behavior, completed-date range usage, and a field list for returned tasks, though it omits ordering or pagination 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?

Front-loads the core retrieval purpose, then covers default and completed-task workflows, followed by a field list. The field list is somewhat long but useful given the absence of an output schema, and there is little wasted wording.

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?

For a read-only list tool with full schema coverage and no output schema, the description covers default/completed retrieval and lists task fields that may be returned. It still leaves some gaps around result ordering, pagination, and the exact return structure.

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%, so the baseline is 3. The description reinforces the default completionStatus behavior and RFC3339 date handling for completed ranges, but most parameter semantics are already in the schema and categoryUUIDs is only implicitly referenced.

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: retrieves tasks from the TODO feature, with default incomplete scope and completed-task filtering. This clearly separates it from sibling write operations like create-task/update-task/delete-task and from get-todo-category-list.

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?

Explains the default behavior and the specific workflow for retrieving completed tasks by setting completionStatus to COMPLETED and supplying completedStartDate/completedEndDate. It does not name alternatives or exclusions, but the when-to-use context is clear.

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