create_or_update_todo

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

No annotations are provided, so the description must fully disclose behavior. It mentions 'intelligently organizes tasks into sections' but doesn't explain the criteria or whether it merges intelligently. It doesn't describe side effects, idempotency, or return values. Vague on how content and markComplete interact.

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 that front-load the main purpose. Every sentence adds information without redundancy. Efficient and clear.

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 tool has 4 parameters and no output schema. The description covers main use cases but lacks details on return value, interaction of parameters (e.g., can content and markComplete be used together?), and the 'intelligently organizes' behavior. More completeness would be beneficial for a complex 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%, so baseline is 3. The description adds value by explaining markdown checkbox format for content, enumerating sections with defaults, and clarifying that markComplete moves tasks to Completed. This goes beyond the schema alone.

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 uses specific verbs ('creates or updates', 'adding tasks', 'marking complete') and identifies the resource ('TODO.md file in .project/ directory'). It clearly distinguishes from sibling tools that handle individual tasks or other files.

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?

Explicitly states when to use: 'when adding tasks, marking items complete, or updating task status'. Does not explicitly state when not to use, but the context of sibling tools (e.g., delete_task, list_tasks) implies alternatives for other operations.

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