bos_customer_delete

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

The description only states 'Delete a customer' without disclosing behavioral traits like soft vs. hard delete, cascading effects on related records, or required permissions. With no annotations provided, the description carries the full burden but fails to provide crucial details for a destructive operation.

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 concise at only four words, which is efficient but under-specified. It lacks necessary details for safe invocation, making it marginally acceptable.

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 potentially destructive action with no output schema and no annotations, the description is incomplete. It omits information about result codes, side effects, failure conditions, and any undo mechanism, leaving the AI agent without sufficient context to use the tool safely.

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 input schema has no descriptions (0% coverage) and the description does not explain the 'customer_id' parameter, such as its format, source, or constraints. For a tool with no parameter documentation, the description should compensate 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 action (delete) and resource (customer), distinguishing it from sibling tools like create or update. However, it lacks additional specifics such as 'permanent deletion' or 'irreversible action', which would have made it more informative.

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., bos_customer_update for deactivation). Prerequisites, such as ensuring the customer has no active orders, are not mentioned.

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