Remove User Data Slot

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

With no annotations provided, the description carries the full burden. It mentions 'Wrapped in undo', indicating the operation is reversible within the undo stack. However, it does not specify if the deletion is permanent after undo stack clearance, or if there are any side effects, which would be valuable for a deletion tool.

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, front-loaded sentence that conveys the essential information with zero waste. Every word is purposeful, making it highly efficient for an AI agent to parse.

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 simple deletion tool with no output schema, the description covers the core operation, identifies the required parameter source, and notes the undo behavior. No critical information is missing, making it complete for the agent to invoke the tool 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 coverage is 100% and the schema already describes desc_id as a DescID path. The description adds value by explicitly linking desc_id to the output of sibling tools (list_user_data or add_user_data), which helps the agent understand how to construct the parameter.

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 'Delete a User Data slot by its DescID path', using a specific verb and resource. It distinguishes from siblings like add_user_data and list_user_data by referencing their return values, making the tool's exact function unambiguous.

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?

Explicitly tells the agent that the desc_id parameter should be obtained from list_user_data or add_user_data, providing a clear retrieval path. It also notes 'Wrapped in undo', implying safe usage. However, it does not explicitly state when not to use this tool or mention alternatives for similar operations.

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