Create Customer

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

No annotations are provided, so the description carries the full burden. It indicates a mutating operation ('Create') and discloses that the request body is passed straight through to Housecall Pro, with a link to the official docs for field names. However, it doesn't disclose response format, error behavior, or any required authentication or permissions, leaving some uncertainty about side effects.

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 two sentences: the first states the purpose, the second gives the key usage instruction and a direct docs link. It's front-loaded, concise, and every sentence earns its place with no wasted words.

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?

While the schema covers the parameter well and the docs link provides field details, the description lacks information about the return value, potential side effects, or any prerequisites. For a create operation with no output schema and no annotations, an agent would benefit from knowing what to expect in the response. The docs link compensates partially, but the description alone is not fully complete.

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 100% coverage for the single 'body' parameter, with a detailed description explaining it's raw JSON and points to the docs. The tool description adds little beyond the schema, reiterating the same info and providing the docs URL. Since the schema already carries the meaning, the description adds marginal value, so a baseline 3 is appropriate.

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 'Create a new customer' with a specific verb and resource, distinguishing it from sibling tools like update_customer and list_customers. The purpose is unambiguous and directly usable by an agent.

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 clear context for when to use the tool—creating a new customer—and instructs the agent to provide a body matching the documented fields. It doesn't explicitly mention exclusions or alternatives, but the purpose is clear enough that an agent won't confuse it with update or list operations.

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