delete_customer

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

Discloses that deletion actually makes the customer inactive, which is important behavioral detail. However, does not explain side effects on associated data, reversibility, or permission requirements.

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?

Extremely concise single sentence with no redundancy. Could be slightly expanded with parameter hints without losing conciseness.

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?

Lacks context about identifying the customer, expected output, error scenarios, and relationship to other operations. Given no output schema and sparse annotations, the description fails to provide sufficient completeness.

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?

Description adds no information about parameters despite schema coverage being only 50%. Does not explain 'idOrEntity' role or usage. The schema provides partial description for 'company', but the description itself contributes nothing.

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?

Description clearly states the action (delete/make inactive) and the resource (customer in QuickBooks Online). It distinguishes this tool from siblings like create_customer, update_customer, and other 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 on when to use this tool vs alternatives like update_customer to inactivate, or when not to use it. Does not mention prerequisites or consequences.

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