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, but fails to disclose critical traits like whether this is a read-only operation, potential rate limits, authentication requirements, pagination behavior, or error handling. For a tool with 8 parameters and no annotations, this is a significant gap.

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 sentence that is front-loaded with the core purpose. It's efficient with no wasted words, though it could be slightly more structured by explicitly listing key filter types. It earns its place by conveying essential information concisely.

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 lacks details on behavioral traits, return format, error cases, or usage scenarios. While the schema covers parameters well, the description doesn't compensate for missing annotations or output schema, making it inadequate for full agent understanding.

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 schema. The description adds minimal value by mentioning 'various filters' and 'both single and batch retrieval', which loosely relates to parameters like 'filter' and 'ids', but doesn't provide additional semantics beyond what the schema already specifies. Baseline 3 is appropriate given high schema coverage.

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 action ('Get a list of tasks') and resource ('from Todoist'), and mentions the filtering capability. It distinguishes itself from siblings like todoist_get_projects or todoist_get_personal_labels by focusing on tasks. However, it doesn't explicitly differentiate from todoist_get_personal_labels or todoist_get_shared_labels in terms of resource type beyond the name.

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 implies usage for retrieving tasks with filters, including batch retrieval via 'ids', but doesn't specify when to use this versus alternatives like todoist_get_projects for projects or todoist_get_personal_labels for labels. It mentions 'handles both single and batch retrieval' which provides some context, but lacks explicit guidance on scenarios or exclusions.

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