updateClient

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Update client information' and does not disclose whether updates are partial or full, whether validation occurs, what happens to unspecified fields, or any side effects. The verb implies mutation but adds no behavioral detail beyond that.

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 one sentence, which is concise and front-loaded. But it is so minimal that it borders on under-specification rather than efficient communication; no structure or extra context is provided.

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?

With a complex nested updates object, no annotations, and no output schema, the description is insufficient. It lacks information about response behavior, error conditions, and the nature of updates (merge vs. replace). An agent would have to infer too much.

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 clientId with a description but the nested 'updates' object lacks description. The tool description adds no parameter semantics; it doesn't explain that 'updates' is a partial update payload or list the editable fields. The property names are self-evident, but the description does not compensate for the 50% schema coverage gap.

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 uses a specific verb ('Update') and resource ('client information'), clearly distinguishing it from addClient (create) and getClients (read). However, it lacks specificity about which client fields are updatable or that it targets existing clients only.

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?

No guidance on when to use this tool versus alternatives like addClient or updateAppointment. There is no mention of prerequisites, context, or exclusions. The usage is only implied by the verb 'Update'.

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