createCustomer

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but 'Create customer' reveals nothing about side effects, required permissions, return values, or operational constraints. It does not contradict annotations (there are none), but it is completely silent on behavior.

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 just two words, which is concise but severely under-specified for a tool with 8 parameters and no other documentation. It is not 'earning its place' as a helpful guide; it is a placeholder that fails to convey necessary information.

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 create operation with 8 parameters, no output schema, and no annotations, the description is wholly inadequate. It does not explain what creating a customer involves, what the parameters mean, or what the response will be, leaving the agent without the context needed to invoke the tool correctly.

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 8 parameters with only 13% description coverage (just a truncated note on customerAttributes). The description adds zero parameter information, failing to compensate for the low schema coverage. The sole required parameter customerId is not even mentioned, making the parameter semantics entirely unclear.

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 'Create customer' clearly states the action (create) and resource (customer), and it distinguishes from sibling tools like getCustomer and deleteCustomer. However, it is essentially a restatement of the tool name without adding any scope or detail, stopping short of the specificity seen in high-quality examples.

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?

The description provides no guidance on when to use this tool versus alternatives such as getCustomer or deleteCustomer. There is no mention of prerequisites, intended scenarios, or exclusions, leaving the agent to infer usage solely from the tool name.

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