get_tasks

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

No annotations are provided, so the description carries full burden. It states 'Get all active tasks,' implying a read-only operation. However, it does not disclose potential issues like rate limits, pagination, or whether all tasks are returned in a single response.

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: two brief sentences followed by a structured Args list. Every sentence adds value, and the information is front-loaded. No redundant or verbose language.

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 tool has three optional parameters and an output schema (not shown but indicated). The description covers the main behavior and parameter semantics, but lacks details on pagination, sorting, or default behavior for active task filtering. Given the simplicity, this is mostly sufficient.

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 0% (no parameter descriptions in schema). The description compensates by explaining each parameter: project_id as optional project filter, label as optional label name, filter_str as Todoist filter string with examples like 'today' and 'overdue'. This adds meaningful context beyond the bare 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 'Get all active tasks' with filter options, specifying the verb (get), resource (tasks), and scope (active). This distinguishes it from siblings like close_task or update_task.

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 mentions filtering options but does not provide explicit guidance on when to use this tool versus alternatives like get_task, search_task_by_name, or list_projects. Some context is implied but not spelled out.

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