delete_purchase

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

With no annotations, the description must fully disclose behavioral traits. It only hints at soft delete with 'make inactive,' but does not explain exact behavior, required permissions, reversibility, or side effects on related data. The description is insufficient for the agent to understand the tool's full impact.

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 a single, front-loaded sentence with no redundant words. It efficiently conveys the core purpose without extraneous 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?

Given the tool has two parameters (one undocumented), no output schema, and no annotations, the description is too minimal. It omits how to use the parameters (especially idOrEntity), expected outcomes, and any context about QuickBooks Online behavior.

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 only 50%: the 'company' parameter has a description, but 'idOrEntity' does not and the tool description does not clarify it. The description adds no meaning beyond the schema, leaving the agent uncertain about how to specify the purchase to delete.

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 that the tool deletes (makes inactive) a purchase in QuickBooks Online, specifying the verb and the resource. It distinguishes from sibling delete tools by naming the entity ('purchase'), making it easy to select among many similar delete tools.

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 (e.g., other delete tools), prerequisites, or when not to use it. The description lacks any context about typical use cases or exclusion criteria.

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