Create Client

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

Annotations are all false, and the description only states the action and requirement. No behavioral details are provided, such as idempotency, error handling, or side effects. The example adds some context but does not enhance transparency beyond the schema.

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 concise with two sentences and an example. Including the Spanish version adds slight redundancy but is acceptable for bilingual support. It is front-loaded with the core action.

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 complexity (5 parameters, nested address object, output schema exists), the description adequately covers purpose, requirement, and usage. It does not detail error conditions or constraints, but with output schema present, missing return value details are acceptable.

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 schema covers all 5 parameters with descriptions. The description adds value by giving a concrete example with typical values (e.g., taxId='B12345678', address object), which helps the agent understand parameter usage beyond the schema.

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 the action ('Create a new client/customer') and resource. It provides an example and distinguishes from siblings like create_client_contact and create_client_note by specifying that clients are used when creating invoices and quotes, which is the core purpose.

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 specifies the minimum requirement ('Requires at minimum a name') and gives context ('Clients are used when creating invoices and quotes'). It does not explicitly list alternatives or exclusions, but the context is sufficient for an agent to understand when to use this tool.

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