get_tasks

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

The description mentions pagination as a behavioral trait, which is useful. However, with no annotations provided, it fails to disclose other important behaviors such as authentication requirements, rate limits, return format, or error handling. A single sentence is insufficient for a read operation with 17 parameters.

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, concise sentence (20 words) that front-loads the main purpose. It could be slightly expanded to cover key behavioral aspects, but it is not verbose. The structure is efficient for a minimal viable description.

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 complexity (17 parameters, no output schema, no annotations), the description is too brief. It omits critical context such as required parameter list_id (though in schema), pagination mechanics, error states, and the structure of the returned data. The description does not fully compensate for the lack of annotations or output schema.

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 coverage is 53%, meaning many parameters already have descriptions. The description adds summary-level context by grouping filter types (status, assignees, tags, date ranges, subtasks, custom fields), which helps an agent understand the overall filtering capability. However, it does not explain individual parameters beyond this grouping, so it provides modest added value.

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 'Get tasks in a List' with specific filter types (status, assignees, tags, date ranges, subtasks, custom fields). It distinguishes from sibling tools like get_task (single task), get_subtasks (subtasks of a specific task), and get_view_tasks (tasks in a view) by focusing on list-scoped retrieval with rich filtering.

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?

No explicit guidance on when to use this tool versus alternatives. The description does not mention when not to use it, prerequisites, or specific scenarios. Given many sibling task-retrieval tools, explicit context would be helpful.

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