create_list_item

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states the mutation ('Create') but does not disclose what the tool returns, whether it overwrites anything, what permissions or validations are required, or what side effects occur on failure. This is a significant gap for a write operation.

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 exceptionally concise: two short sentences with no filler. The purpose is front-loaded, and the second sentence adds useful parameter semantics. Every word earns its place.

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 simple three-parameter create operation, the description gives the essential action and the key fields_json format. It is minimally viable, but it leaves gaps: no return value information, no usage guidance, no examples, and no explanation of list/site ID semantics beyond their 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 0%, so the description must compensate. It does add meaningful context by explaining that fields_json is a 'JSON object of {columnName: value}', which is the most complex parameter. However, it does not explain how to obtain site_id or list_id, provide an example, or clarify whether columnName refers to internal or display names.

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 a specific verb and resource: 'Create a list item.' This clearly distinguishes it from sibling tools like update_list_item, delete_list_item, get_list_item, and list_list_items at a basic level. However, it does not explicitly differentiate it from broader 'create' tools that might apply to similar list-like resources.

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 provides no guidance on when to use this tool versus alternatives such as update_list_item, append_table_row, or create_todo_task. There is no mention of prerequisites like needing an existing list, appropriate column names, or situations where update_list_item would be more appropriate.

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