roiq_delete_item

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

The description discloses cascading deletion for boards/tables and the need for user confirmation, which are critical behavioral traits. With no annotations, the description covers the main side effects 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 two sentences long, front-loaded with the core action, and contains no unnecessary words. It is efficient and easy 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 single-parameter deletion tool with no output schema, the description covers the action and a behavioral note. However, it lacks details on return values, error conditions, or prerequisites, making it adequate but not thorough.

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 0%, and the description only mentions the 'id' parameter implicitly ('por su id') without adding format, constraints, or examples. This provides minimal additional value beyond the parameter name.

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 action ('Elimina un item') and resource ('por su id'), and adds a specific case (if board/table, also deletes its cards). This distinguishes it from sibling tools like roiq_rename_item or roiq_update_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 description advises confirming with the user before deleting important items, but does not provide explicit when-to-use or when-not-to-use guidance compared to alternatives like roiq_rename_item or roiq_list_items.

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