Update client

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds minimal behavioral context. It does not disclose whether updates are partial or full, what happens to omitted fields, or any permission requirements. This lacks transparency for a mutation tool.

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 short sentences, with the verb and resource front-loaded. No word is wasted, and the advice about 'extra' is immediately actionable.

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 simple update tool, the description covers the core purpose but lacks details such as response format, partial update behavior, or required permissions. With no output schema and minimal parameter documentation, the description could be more complete, but it is adequate for straightforward use.

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 describes client_id only, leaving five parameters undocumented. The description adds meaning to 'extra' by explaining it as a catch-all for any other Upmind client field, which is helpful. However, notes, lastname, firstname, and public_name remain undefined without any elaboration in the description.

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 tool's function: 'Update client profile fields.' This is specific to the client resource and distinguishes it from sibling tools like create_client or list_clients. The mention of 'extra' for any other Upmind client field further clarifies the scope.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention conditions, prerequisites, or exclusions. The only guidance, 'Use "extra" for any other Upmind client field,' is about parameter handling rather than tool selection.

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