missive_list_tasks

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

Annotations already declare readOnlyHint=true, which the description supports accurately. The description adds details about pagination behavior (cursor-based, no offset) and optional organization filtering, contributing beyond annotations. However, it does not disclose rate limits or auth requirements.

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 concise sentences that immediately state the purpose and ordering, then cover filtering and pagination. No wasted words; information is front-loaded.

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?

With 10 parameters and no output schema, the description covers ordering, filtering, and pagination well. However, it lacks details about the return structure (e.g., fields in each task object). Given complexity, this is a notable gap.

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 baseline is 3. The description adds value by clarifying pagination mechanics ('there is no offset') and noting that `organization` is optional with a default. This extra context raises the score above baseline.

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 tool lists tasks with ordering by last activity. It distinguishes from siblings like missive_get_task (single task) and missive_create_task. However, it does not explicitly differentiate from other list tools like missive_list_conversations, though the mention of task-specific filters helps.

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 explains filtering options and pagination with `until` and notes no offset. It provides some guidance on how to use the tool but does not specify when to use this tool versus alternative tools (e.g., missive_get_task for a single task) or when not to use it.

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