tfs_create_work_item

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

The description states 'Create' implying mutation but lacks details on required permissions, error handling, or what happens with invalid fields. Since no annotations are provided, the description carries the full burden, which it does not fulfill adequately.

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 extremely concise with two sentences, front-loading the core verb and resource. No unnecessary words; every sentence adds value.

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?

With 4 parameters (2 required), a nested object, no output schema, and no annotations, the description is too minimal. It does not explain the return value, mandatory title param, or process behavior, leaving significant gaps for an agent.

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 50% (type and fields have descriptions). The description adds examples for 'type' and explains 'fields' as a map of reference names to values, but it omits 'title' (required) and 'project', failing to compensate fully for 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 work item' and mentions the type parameter with examples (Bug, Task, User Story), which distinguishes it from sibling tools like query, update, or get. However, it does not explicitly mention the required 'title' parameter, slightly reducing clarity.

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 like tfs_update_work_item or tfs_query_work_items. The description does not mention prerequisites, restrictions, 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.