set_customer_status

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

No annotations provided, so description carries full burden. Only states 'Set a customer's status' without disclosing side effects, auth requirements, error handling, or reversibility. Very minimal transparency.

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?

Single concise sentence, no wasted words. However, it is under-specified and lacks necessary detail, which is not a virtue of 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?

Description is incomplete for a mutation tool with no output schema. Missing return value, error conditions, prerequisites (e.g., customer existence). Sibling tools provide alternative actions, but no context on when to use this one.

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 coverage is 0%, so description must add meaning. It specifies allowed status values but contradicts itself by referencing 'business name' when the parameter is 'customer_id'. Does not explain the customer_id parameter or any constraints.

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 (set) and resource (customer status), lists allowed values (active/on_hold/closed). However, it mentions 'by business name' while the parameter is customer_id, introducing minor confusion. Distinguishes from sibling tools like get_order_status.

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 explicit guidance on when to use this tool versus alternatives like lookup_customer or release_hold. Usage is implied only by the description of the action.

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