create_todo

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

With no annotations, the description carries the full burden. It discloses that the operation is for the authenticated user and that the date defaults to today in Asia/Seoul, which adds useful behavioral context. It does not mention persistence, idempotency, or side effects beyond creation.

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 two sentences with no filler and the primary operation is front-loaded. It is concise and readable, though it sacrifices completeness for 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?

For a 3-parameter create tool with no output schema and no annotations, the description is under-specified. It does not clarify what a goal_id is for, what the response contains, or the exact format expected for the day parameter. The timezone default is helpful but not enough.

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 must compensate for all parameters. It adds semantic meaning for 'day' by explaining the default timezone behavior, but says nothing about 'content' or 'goal_id'. The purpose of 'goal_id' is entirely 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 states a specific verb ('Create') and resource ('a todo'), and scopes it to the authenticated user. This clearly distinguishes it from sibling tools like get_todo, update_todo, complete_todo, and delete_todo.

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 usage context is implied: use this when creating a new todo. However, there is no explicit guidance about when not to use it or how it relates to alternatives such as update_todo or complete_todo.

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