customers.create

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

With no annotations provided, the description carries the full burden of disclosure but only implies mutation through the verb 'Create'. It fails to specify idempotency behavior, error handling for duplicate emails, or what the tool returns upon success.

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?

While brief and front-loaded, the single sentence is overly terse to the point of under-specification. It communicates the basic operation but wastes no words, though it fails to earn its place by adding value beyond the tool name.

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?

Inadequate for a creation tool with 4 parameters including a nested metadata object. Without annotations, output schema, or schema descriptions, the description should explain the customer creation workflow, return values, and field semantics, none of which are present.

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?

With 0% schema description coverage, the description must compensate by explaining parameters, but it mentions none. Critical details about the metadata object structure, email validation requirements, and optional vs required fields (only email is required) are completely absent.

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?

States the basic action (create) and resource (customer) but fails to differentiate from sibling creation tools like accounts.create or persons.create, which is critical given the large number of similar operations available.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., accounts.create) or prerequisites (such as email uniqueness constraints). No mention of whether this is for new customers only or if it updates existing ones.

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