Create Things 3 Todo

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

Annotations indicate readOnlyHint=false (write operation) and destructiveHint=false (not destructive), which aligns with creation. The description adds that it returns {id, name}, but does not elaborate on side effects like idempotency or notifications. Given the tool's nature, this is adequate.

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 and well-structured: a summary sentence, a list of arguments with brief explanations, and a return note. Every sentence adds value without 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?

With 8 parameters and no output schema, the description covers all parameters, explains return type ({id, name}), and provides usage hints (e.g., 'tags must already exist'). No gaps remain for an AI agent to use it correctly.

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. The description adds significant value by detailing the 'when' format (today, evening, YYYY-MM-DD), requiring tags to exist, projectId from get_projects, heading requiring projectId, and checklistItems as strings. This goes beyond the raw 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 it creates a new todo in Things 3, lists supported features (title, notes, scheduling, etc.), and distinguishes it from sibling tools like complete, delete, update. The verb 'create' and resource 'todo' are specific.

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 when to use the tool (to create a todo) and provides context via sibling tool names. However, it does not explicitly state when not to use it or compare with alternatives. It is clear enough for an AI agent given the sibling context.

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