todoist_filter_create

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

Without annotations, the description carries the full burden. It discloses the plan requirement, which is a behavioral constraint. However, it does not mention idempotency, side effects (e.g., overwriting existing filters with the same name), rate limits, or the return value. For a create tool, more detail would be beneficial.

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 two sentences long. The first sentence clearly states the tool's action and resource. The second sentence adds essential context about query syntax and a prerequisite. There is no redundant or unnecessary information.

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 description lacks details about the return value (e.g., the created filter object), potential errors (e.g., duplicate name, invalid query), and behavior on success vs failure. For a create operation with no output schema, more information is needed to complete the picture. The prerequisite mention is useful but insufficient.

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%, so the schema already documents all 5 parameters. The description adds query syntax examples, which are helpful but largely duplicate the schema's examples for the 'query' parameter. The description does not add significant new meaning beyond the 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 explicitly states 'Create a new custom filter in Todoist' using a specific verb and resource. It differentiates from sibling tools like todoist_filter_get, todoist_filter_update, and todoist_filter_delete by naming the action 'create'. Examples of query syntax further clarify the tool's purpose.

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 provides clear context: it mentions the Todoist query syntax and the requirement for a Pro or Business plan. This helps an agent know when to use this tool (e.g., when a filter needs to be created and the user has the right plan). It doesn't explicitly state when not to use it or mention alternatives, but the sibling list implies other tools for different operations.

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