Add client

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

Annotations already declare non-readOnly, non-destructive, non-idempotent and open-world. The description adds genuinely useful behavior beyond that: nothing is sent at creation time, while appointment_messages=true triggers booking confirmations and reminders across email/SMS/WhatsApp, and marketing records consent. It does not cover duplicate-client handling or failure modes.

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 second sentence opens with a circular restatement ('Adds a client as Add client in the Client list does'), which wastes space before the genuinely useful message-consent explanation. The final sentence is well placed and front-loads the important 'nothing is sent' fact late.

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 7-parameter mutation with no output schema, the description covers the essential creation semantics and the non-obvious messaging side effects. Gaps are modest: no mention of duplicate-email behavior or what identifying data comes back.

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 description coverage is 100%, so the schema already documents all seven parameters including defaults and the phone pattern. The description adds only light reinforcement of the appointment_messages/marketing effect, and even refers to 'mobile' where the schema calls the field 'phone'.

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 a specific verb and resource: 'Add a client to the business's client list.' An agent can distinguish it from list_clients/get_client/add_client_note by the verb, though no sibling is named explicitly.

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?

Usage is implied by the create verb, but there is no explicit guidance on when to use this versus alternatives (e.g., checking for an existing client first, or using add_client_note for notes). No exclusions or prerequisites are stated.

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