delete_item_position

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description aligns with that. The description adds no extra detail about side effects, permanence, or constraints. Since annotations cover the safety profile, there is no contradiction, but no added behavioral context.

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 extremely short and front-loaded with the action verb, but it is grammatically awkward ('a item') and lacks any supporting detail. It is concise but under-specified for a destructive operation.

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 delete tool with rich schema and annotations, the description is minimally sufficient. However, it lacks any explanation of what an item position is or the document types it applies to (which the schema provides), and no output/return behavior is noted, leaving some gaps for an agent.

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 descriptions cover 100% of parameters, including a helpful example for document_id and an enum explanation for kb_document_type. The description itself adds no parameter-specific meaning, so baseline 3 is appropriate.

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 uses the verb 'Delete' and clearly identifies the resource as 'item position', making the core action unambiguous. It does not, however, distinguish this from sibling position-deletion tools like delete_subposition or delete_default_position, nor does it specify the document context beyond the schema enum.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention that item positions belong to quotes/orders/invoices (that's only in the schema) or when a delete_subposition would be more appropriate. There are no usage contextual cues in the description itself.

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