delete_item

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

No annotations are supplied, so the description carries the full behavioral burden. It does earn credit for disclosing the non-obvious soft-delete semantics ("make inactive"), which tells an agent the record is not physically removed. However it says nothing about reversibility, referential effects on existing transactions that use the item, required permissions, or error behavior for an invalid or already-inactive item — significant gaps 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 tight sentence with zero redundancy, and the soft-delete clarification sits immediately after the verb so the most important nuance is front-loaded. It is efficient, though the terseness borders on under-specification for a mutation tool.

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 destructive mutation with no annotations, no output schema, and a nested untyped parameter object, the definition does not give an agent enough to call it safely. Missing are the ID-vs-entity input format, permission expectations, effects on linked transactions, reactivation path, and any notion of the return value.

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 description coverage is 0% and the single parameter is declared as an untyped, undescribed empty object named "idOrEntity", with a nested params object whose additionalProperties are unconstrained. The description adds no meaning at all — it never explains whether to pass a bare ID string or a full entity object, nor which fields the entity form needs. With full burden on the description, this is a clear shortfall.

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 gives a specific verb plus resource ("Delete ... an item") and scopes it to QuickBooks Online, which separates it from delete_invoice, delete_customer, delete-vendor and the many other delete siblings. It also parenthetically clarifies that deletion is a soft delete ("make inactive"), which is the one thing an agent could not guess. It stops short of explicitly naming the alternatives, but the resource noun does the disambiguating work.

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?

There is no guidance on when to choose this tool over update_item (the natural way to reactivate an inactive item) or read_item (to confirm the item exists first). No prerequisites, no mention of what happens when the item is already inactive, and no exclusions. The usage decision is entirely left to inference.

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