delete_work_item_property_value

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds valuable context: it deletes 'value(s)' and for multi-value properties, all values are deleted. This goes beyond annotations, but it doesn't mention error cases or success response. No contradiction with annotations.

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 concise and front-loaded with the main action. The multi-value behavior note is important. The Args list is somewhat redundant with the schema but provides extra context. No wasted sentences.

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 destructive nature (annotations) and absence of output schema, the description should clarify success/failure behavior, error conditions (e.g., property not found), and idempotency. It only covers the multi-value nuance. The agent is left wondering what happens upon execution.

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?

With 0% schema coverage, the description bears the burden. It adds labels like 'UUID of the project' etc., providing basic semantic mapping. However, it doesn't add constraints like format validation, immutability, or relationships. For 3 parameters, this is adequate but minimal.

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 tool deletes value(s) of a custom property on a work item, specifying it's for custom properties and clarifying behavior for multi-value properties. This distinguishes it from siblings like set_work_item_property_value (set) and delete_work_item_property (delete property definition).

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 implies usage (when you want to delete a property value) but does not explicitly guide when to use this over alternatives, nor does it mention prerequisites (e.g., property must exist) or when not to use it. The clarification about multi-value behavior is helpful but not comprehensive guidance.

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