todoist_get_tasks

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

No annotations are provided, so the description carries the full burden. It mentions 'handles both single and batch retrieval', which adds some behavioral context beyond the input schema. However, it lacks critical details such as whether this is a read-only operation, how results are paginated or limited, error handling, or authentication requirements. For a tool with 8 parameters and no annotations, this is insufficient.

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, efficient sentence that front-loads the core purpose ('Get a list of tasks from Todoist') and adds qualifying details. There's no wasted text, though it could be slightly more structured by separating filtering and retrieval aspects into distinct points.

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 complexity (8 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain return values, error conditions, or behavioral constraints like rate limits or side effects. For a tool that likely returns structured task data, more context is needed to guide effective usage, especially without 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 description coverage is 100%, meaning all parameters are documented in the input schema. The description adds minimal value by implying filtering capabilities ('various filters') and retrieval modes ('single and batch'), but doesn't provide additional syntax, format details, or interactions between parameters beyond what the schema already specifies. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('Get') and resource ('list of tasks from Todoist'), and specifies the action involves 'various filters' and 'both single and batch retrieval'. It distinguishes itself from siblings like todoist_get_projects or todoist_get_personal_labels by focusing on tasks, but doesn't explicitly differentiate from other task-related tools like todoist_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 'various filters' and 'both single and batch retrieval', which implies usage for filtered or specific task retrieval. However, it provides no explicit guidance on when to use this tool versus alternatives like todoist_get_projects for project-level data or todoist_update_task for modifications. No exclusions or prerequisites are stated.

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