create_work_item

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the create behavior is expected. The description adds contextual behavior: prerequisite parameter requirements, date formatting, and priority enum values. It doesn't contradict annotations, and adds meaningful operational context beyond what annotations provide.

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 three sentences, front-loaded with purpose, then dependencies, then format notes. Each sentence earns its place, with no fluff or repetition of schema details.

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 high-complexity tool (15 params, no output schema), the description covers the core dependencies and key format constraints. It does not mention what the response includes (e.g., created work item ID), but given the wealth of other guidance, this is a minor omission.

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 coverage is 0%, so the description carries the burden. It explains sources for several critical parameters (project_id, state_id, assignees, labels) and gives valid values for priority and date format. However, it does not explain many optional parameters like type_id, parent_id, sort_order, external_id, or description_html, leaving some gaps.

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 new work item (issue) in a project' with a specific verb and resource. It distinguishes from sibling tools like update_work_item and delete_work_item by focusing on the creation action, and includes the key target ('work item (issue)').

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?

Provides explicit dependencies: 'Requires project_id from list_projects', and names specific tools to source other parameters (list_states, get_workspace_members, list_labels). It also gives format and enum constraints for dates and priority, which is actionable guidance for correct invocation.

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