todoist_create_project

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

With no annotations provided, the description carries full burden but offers minimal behavioral disclosure. It mentions 'nested hierarchies' which hints at parent-child relationships, but doesn't cover important aspects like permissions needed, whether creation is idempotent, error handling, or what happens when parent_name doesn't exist. For a creation tool with zero annotation coverage, this is insufficient.

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, efficient sentence that front-loads the core functionality ('Create one or more projects') and adds key features ('with support for nested hierarchies'). Every word earns its place with no redundancy or unnecessary elaboration.

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?

For a creation tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, authentication requirements, or how batch operations interact with nested hierarchies. The schema provides parameter details but the description lacks necessary behavioral context.

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%, providing comprehensive parameter documentation. The description adds minimal value beyond the schema by mentioning 'nested hierarchies' (relating to parent_id/parent_name) and 'batch operations' (relating to the projects array), but doesn't explain parameter interactions or usage patterns. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('Create') and resource ('projects'), specifying support for batch operations and nested hierarchies. It distinguishes from siblings like 'todoist_update_project' by focusing on creation rather than modification, but doesn't explicitly contrast with 'todoist_get_projects' for retrieval.

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?

No guidance is provided on when to use this tool versus alternatives like 'todoist_update_project' for modifying existing projects or 'todoist_get_projects' for retrieval. The description mentions batch operations and nested hierarchies but doesn't specify when these features are appropriate.

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