delete_transfer

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

The description is extremely minimal and does not disclose any behavioral traits beyond the bare action. No annotations are present, so the description must convey safety, side effects, or required permissions, but it fails to do so. This could mislead an agent into believing it's a benign deletion without consequences.

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 very short (one sentence), which is concise but lacks necessary detail. It is front-loaded, but the brevity detracts from its usefulness.

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 complexity of a delete operation with nested parameters and no output schema, the description is incomplete. It fails to explain return values, side effects, or required context such as company identification.

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?

The schema covers 50% of parameters (only 'company' has a description). The description does not add any meaning for the 'idOrEntity' parameter within 'params', leaving its semantics unclear. With low schema coverage, the description should explain the parameter's purpose but does not.

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 verb 'delete' and the resource 'transfer', specifying the domain 'QuickBooks Online'. This provides a clear purpose, though it does not distinguish it from other delete tools in the sibling list.

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. There is no mention of prerequisites, conditions, or when not to use it, which is problematic given the many sibling delete operations.

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