create_todo_item

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

With no annotations, the description carries the full burden, but it only explains parameter semantics. It does not disclose side effects, required permissions, whether notifications are actually sent, or what happens if the list does not exist. The 'notify' parameter is mentioned but not elaborated on.

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 appropriately sized and front-loaded with a one-sentence summary, followed by a clean Args list. Every sentence provides useful information with no 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?

The tool has 5 parameters and an output schema, so the description adequately covers parameter roles. However, it lacks usage context such as typical workflows, prerequisites (e.g., the todo list must exist), or behavior when required parameters are invalid. It is minimally viable but not rich.

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 0%, so the description fully compensates by providing a clear explanation for each parameter. It correctly notes optionality for responsible_party_id and due_at, and adds format details (YYYY-MM-DD) and the meaning of notify. This is valuable beyond the bare 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 begins with 'Create a new to-do item in a to-do list,' using a specific verb and resource. This clearly distinguishes it from sibling tools like update_todo_item, complete_todo_item, and delete_todo_item.

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 explicit guidance is given about when to use this tool versus alternatives, nor are conditions or prerequisites mentioned. The description implies creation use but offers no exclusions or comparisons to sibling tools.

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