kaiten_delete_select_value

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

With no annotations, the description carries the full burden. It does disclose one important behavioral trait—soft deletion via a deleted flag—which prevents assuming permanent removal. However, it omits side effects, reversibility, permissions, and return behavior, which are relevant for a mutation 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?

A single 9-word sentence that front-loads the action and the key qualifier ('soft'). There is no filler; every word contributes useful information.

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 two-parameter delete, the description plus the fully covered schema is adequate for basic invocation. However, with no output schema and no annotation context, the agent is left without post-invocation expectations or knowledge of consequences for existing data.

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%, so the baseline is 3. The description adds no parameter-level meaning beyond the schema's 'Select value ID' and 'Property ID', and it does not explicitly state that value_id must belong to the given property_id.

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 states a specific action ('Delete (soft)'), a specific resource ('a select value'), and the mechanism ('marking it as deleted'). This distinguishes it from hard-delete operations and from sibling tools like kaiten_delete_custom_property or kaiten_delete_card.

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 intended use is implied by the verb and resource, but there is no explicit when-to-use, when-not-to-use, prerequisites, or alternatives. It does not clarify whether this should be preferred over update_select_value for hiding a value, nor what happens if the value is in use.

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