todoist_reminder_create

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

Discloses the plan requirement (Pro or Business) as a behavioral constraint. Without annotations, description carries burden but does not detail side effects, auth needs, or success/failure outcomes beyond plan.

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?

Two concise sentences front-loaded with purpose. Every sentence earns its place with no redundancy.

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 complete schema and many parameters, description covers core function and plan requirement but lacks details on return value, error handling, or guidance for choosing between task_id and task_name.

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 100%, so baseline is 3. Description adds minimal value beyond schema by summarizing types, but does not provide further meaning for parameters like task_id vs task_name disambiguation.

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?

Clearly states 'Create a new reminder for a task' with specific verb and resource. Mentions three reminder types, distinguishing the creation action from sibling tools like delete, get, update, but does not explicitly differentiate from them.

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?

Implies usage by listing supported reminder types and plan requirement, but lacks explicit when-to-use or when-not-to-use guidance. No mention of alternatives like updating an existing reminder.

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