Create Things 3 Project

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

Annotations show no destructive or read-only hints. Description adds return format ({id, name}) and a key precondition (tags must already exist), enhancing transparency beyond annotations.

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?

Concise docstring with clear purpose, structured Args, and Returns line. No wasted words; front-loaded with the action.

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?

Covers all parameters, return value, and a key precondition (tags existence). No output schema, so return info is helpful. Could mention error handling but adequate for a simple creation tool.

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%, but description adds practical guidance: examples for 'when' values and directs user to things3_get_areas for areaId, going 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?

Description explicitly states 'Create a new project in Things 3', specifying the verb and resource. It clearly distinguishes from sibling tools like things3_create_todo, which creates a todo instead.

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?

Context is clear: this tool is for creating projects, while siblings handle todos. No explicit 'when not to use' but the grouping makes usage obvious.

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