new_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 only says 'Create', which implies mutation, but lacks details about side effects, required permissions, idempotency, or what happens on success/failure. The 'for current project' scoping adds some context but is minimal.

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 a single sentence, front-loaded with the action, and contains no filler or redundant information. It efficiently conveys the tool's core purpose.

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 has 6 parameters, no output schema, and no annotations, a one-sentence description is insufficient. It does not explain the return value, how required fields are used, or the meaning/side effects of parameters like priority and parent_id. The description is adequate for a basic understanding but far from complete for safe invocation.

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 100% per the metric, so the baseline is 3. The description adds value by enumerating possible values for item_type (issue, todo, feature, epic, diary entry), but other parameters like priority, complexity, and parent_id remain only minimally described by their 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 clearly states the action ('Create') and the resource ('a new issue, todo, feature, epic, or diary entry'), and scopes it to the current project. This distinguishes it from siblings like edit_item and delete_item.

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 clearly indicates this tool is for creating new items in the current project, which provides clear context. However, it does not explicitly mention when not to use it or name alternatives, but the creation purpose is evident.

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