create_item

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a creation operation, implying it's a write/mutation tool, but doesn't cover critical aspects like required permissions, whether the operation is idempotent, error handling, or what happens on success (e.g., returns the new item ID). The format hints for person and date fields are useful but insufficient for full transparency.

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 highly concise and front-loaded, with every sentence earning its place. The first sentence states the core purpose, and the subsequent sentences provide essential formatting details without redundancy. There's no wasted verbiage, making it efficient for an agent to parse.

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's complexity (a write operation with 2 parameters, nested objects, and no output schema), the description is partially complete. It covers the purpose and parameter formatting well but lacks behavioral context (e.g., permissions, response format) and usage guidelines. Without annotations or an output schema, these gaps are notable, though the parameter guidance helps mitigate some issues.

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?

The description adds significant value beyond the input schema, which has 50% coverage (only the 'fields' parameter has a description). It explains that 'fields' should be key-value pairs using internal column names and provides specific formatting rules for person fields (using userId) and date fields (ISO 8601 strings). This compensates well for the schema's gaps, though it doesn't detail 'listName' beyond what's implied by the purpose.

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 verb 'Create' and the resource 'new item in a list', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'create_list' or 'update_item', which would require mentioning that this tool is for adding items to existing lists rather than creating lists themselves or modifying existing 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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., that the list must already exist), exclusions, or comparisons to siblings like 'create_list' (for creating lists) or 'update_item' (for modifying items). This leaves the agent without context for tool selection.

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