delete_project_items

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

Since no annotations are provided, the description must convey the high risk associated with this action. While the verb 'Delete' implies destruction, the lack of any warning, irreversibility note, or operational context fails to properly disclose the behavioral risks of this 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?

The description is perfectly concise, stating the function in a single, direct sentence with no wasted words.

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?

As a destructive tool with no output schema, the description is incomplete. It lacks any safety context, confirmation steps, or crucial warnings necessary for an agent making a high-impact mutation call.

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 schema already explains that 'nodeIds' is an 'Array of nodeIds to delete.' The description provides no semantic information beyond what is already structurally defined for the single input 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 tool clearly identifies the action (Delete) and the target resource (project items). However, given the large number of related siblings like 'get_project_items' and 'rename_project_item', it fails to differentiate itself or state what exactly constitutes a 'project item.'

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 by stating it deletes items 'from the project panel.' However, it offers no guidance on when *not* to use it, or if there are specific constraints (e.g., item status) that should prevent deletion.

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