filter_tasks

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

With no annotations, the description must disclose behavioral traits. It implies a read operation by mentioning 'Returns: Filtered tasks with statistics', but does not explicitly state that no modifications occur, nor does it mention authentication needs, rate limits, or any side effects.

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 concise with one summary line followed by a structured Args/Returns section. It is front-loaded and every sentence provides value, though the code-like style could be slightly tightened.

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 4 parameters and an existing output schema, the description covers the tool's purpose, parameters, and return value. It lacks detail on 'bulk operation support' and edge cases, but is otherwise complete for a filtering tool.

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 0%, so the description compensates by explaining each parameter: project_id as 'ID of the project', status with an example list, limit as 'Maximum number of tasks to return', and use_last_tasks as 'Use efficient last 200 tasks endpoint'. This adds meaningful context beyond the raw 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 clearly states 'Filter tasks by multiple criteria with bulk operation support', indicating the verb (filter), resource (tasks), and scope (multiple criteria). It distinguishes from sibling tools like list_tasks by highlighting bulk operation support, though it does not explicitly differentiate from similar filter tools.

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 guidance is provided on when to use this tool versus alternatives (e.g., list_tasks or get_task). There is no mention of prerequisites, when-not-to-use, or suggestions for alternative tools based on different needs.

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