todo_add_item

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

No annotations are provided, so the description must carry the full behavioral burden. It only mentions the action and a due_date format hint, lacking details on side effects, error cases, or entity_id validation.

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 short (2 sentences) with no fluff, but it could be better structured by front-loading the core purpose and then explaining parameters. It is efficient but not optimally organized.

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?

Despite low complexity and the presence of an output schema, the description is incomplete: it fails to clarify what 'entity_id' (likely a todo list identifier) and 'item' (the todo text) mean, leaving ambiguity for an agent.

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?

With 0% schema description coverage, the description should explain all parameters. It only clarifies 'due_date' format, leaving 'entity_id', 'item', and 'description' completely unexplained.

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 explicitly states 'Add a new item to a todo list', which is a specific verb+resource pair. It clearly distinguishes from sibling tools like todo_remove_item and todo_list_items.

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?

The description implies usage for adding items but provides no explicit guidance on when to use this tool versus alternatives, nor any when-not-to conditions or prerequisites.

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