bos_customer_address_delete

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

No annotations exist, and the description only states 'delete' without disclosing irreversibility, required permissions, or side effects (e.g., impact on related orders or addresses). The tool's destructive nature is implied but not explicitly warned.

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 short sentence, which is concise but severely under-specified for a deletion tool. It lacks upfront key details needed for safe invocation, making it more an omission than 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?

Given the lack of annotations, output schema, and parameter descriptions, the description provides minimal context. For a CRUD deletion operation, important details like confirmation steps, cascading effects, or return status are missing.

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 0% description coverage, and the description adds no information about the two required parameters (customer_id, address_id). The agent receives no guidance on what values to provide or their purpose beyond the schema structure.

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 'Delete a customer address' clearly states the action and resource, but does not differentiate from sibling tools like bos_customer_address_create or bos_customer_address_list. It lacks specificity about the scope (e.g., deleting an existing record).

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., when to choose delete over update or deactivate). No context about prerequisites or consequences.

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