add_item

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

Annotations provide readOnlyHint=false and destructiveHint=false, indicating a mutation but no destruction. The description adds that it creates an item, which aligns, but does not disclose side effects, permissions needed, or return behavior. Since annotations are minimal, the description should provide more context about what happens after 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 of clear, concise language. It front-loads the purpose immediately and provides essential context without any redundant or verbose content. Every word contributes to understanding.

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 five parameters with full schema coverage, no output schema, and minimal annotations, the description provides adequate context for a creation tool. It explains what items are and where they belong. However, it could be slightly improved by mentioning that the tool returns the created item or its ID, but it is still fairly complete.

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?

All five parameters have schema descriptions (100% coverage), so the schema already documents their purpose. The description adds context by explaining that reference_table and reference_id refer to parent entities (task, subtask, sidequest), but this is implicit from the parameter descriptions. The description does not significantly enhance parameter understanding beyond the 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 clearly states 'Create a single work item under a task, subtask, or sidequest', specifying the exact action and the parent entities. It also defines items as 'the smallest trackable units of work', distinguishing them from larger structures like tasks or subtasks, which are handled by sibling tools like add_task or add_subtask.

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 when to use the tool (to create a smallest work unit under a parent) but does not explicitly state when not to use it or mention alternatives. For example, it does not clarify that add_items (plural) might be used for batch operations, or that this tool is for single additions.

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