checkvist_get_tasks_paginated

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the bar is lower. The description adds the chunking/pagination context and mentions avoiding size limits, but it doesn't disclose details like how the end of the list is signaled or any error behavior.

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 two sentences with no filler. It front-loads the core purpose (get all tasks in chunks) and immediately explains the usage pattern, earning every word.

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 description covers the pagination concept and how to iterate, but with 5 parameters and no output schema, it lacks guidance on determining when the last page is reached and when/how to use compact modes. It is minimally viable but leaves gaps for a complete 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?

Schema description coverage is 100%, so the baseline is 3. The description only mentions 'page numbers' but does not add meaning beyond the schema for parameters like compact, max_depth, or ultra_compact. It neither compensates nor detracts from the schema.

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 uses a specific verb 'Get ALL tasks in chunks' and clearly identifies the resource (tasks) with a pagination mechanism, setting it apart from siblings like get_tasks or get_task_tree. It explicitly states the page-based approach, making the tool's purpose unambiguous.

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 says 'Call multiple times with different page numbers to read entire checklist', providing a clear when-to-use pattern for reading all tasks in a checklist. While it doesn't explicitly name alternative tools, it gives enough context for the paginated use case.

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