delete_work_item_property

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains scope resolution but omits critical destructive traits: whether deletion is permanent, if it cascades to values or options, or if special permissions are required. A delete tool needs to state such consequences, and this description is too sparse.

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 efficiently structured: a one-line summary followed by a compact Args list. Every sentence provides necessary information, and the scoping instructions are concise. No fluff or repetition.

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?

The tool's parameters and scope logic are well-covered, satisfying the core complexity. However, for a destructive delete operation with no output schema, the description should indicate what response to expect (e.g., success/failure) or whether the deletion is irreversible. This absence leaves the agent guessing about the operation's outcome, making completeness partial.

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?

The schema provides no per-parameter descriptions (0% coverage), but the description compensates fully. Each parameter is explained with type (UUID) and scoping rules (e.g., 'Omit for workspace scope'). The conditional guidance for project_id and work_item_type_id adds semantic depth beyond the schema, making parameter usage clear.

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 opens with 'Delete a work item property by ID,' clearly stating the verb, resource, and identification method. This distinguishes it from sibling tools like delete_work_item_property_option and delete_work_item_property_value, which target different resource types.

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 provides scoping guidance by explaining when to omit project_id (workspace scope) and work_item_type_id (project-level endpoint), giving the agent clear conditional usage context. However, it does not explicitly compare alternatives or state when not to use this tool, so it stops short of a 5.

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