create_work_item

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

The description only states that the tool creates a work item, which implies mutation, but does not disclose side effects, required permissions, rate limits, or any other behavioral traits. Since no annotations are present, the description carries the full burden and fails to provide sufficient 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 a single, short sentence with no wasted words. It is appropriately front-loaded but could benefit from slightly more detail without becoming verbose.

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 13 parameters, no output schema, and no annotations, the description is severely lacking. It fails to mention key relationships (e.g., projectId, boardId) or what the tool returns, making it incomplete for an agent to use correctly.

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 46% (only 6 of 13 parameters have descriptions in the schema). The tool description adds no additional meaning to any parameter, relying entirely on the schema. It does not compensate for the low coverage.

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 ('Create') and resource ('work item (task)') and clarifies the context ('in a project'), which clearly distinguishes this tool from siblings like 'clone_work_item' or 'update_work_item'. It also specifies that a work item is a task, adding precision.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., cloning or updating work items). There is no mention of prerequisites (e.g., the project must exist) or when not to use it.

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