create_todo

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

With no annotations provided, the description must fully disclose behavioral traits. It only states 'Create a new todo list' without mentioning side effects, success conditions, duplicate handling, or any other behavioral details. This is insufficient for an AI agent to understand the tool's full impact.

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 very short (5 words), which makes it concise but too minimal. It lacks important details such as what constitutes a 'todo list' or how the content should be formatted. While front-loaded, it sacrifices informative value at the expense of brevity.

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 the tool has three required parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain the return value, the format of the content parameter (markdown checklist), or any constraints like uniqueness of names.

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% with each parameter having a clear description. The tool description does not add any additional meaning beyond what is already in the schema, thus meeting the baseline of 3.

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 action ('Create') and the resource ('a new todo list'), using a specific verb+resource pattern. However, it does not differentiate from sibling tools like update_todo or list_todos, but the resource name is distinct enough from other create_* tools.

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 alternative tools such as update_todo or delete_todo. The description lacks any context about prerequisites, exclusions, or suggested scenarios.

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