update_client

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

No annotations provided. Description states it updates (mutation) and partial update behavior. Lacks disclosure of side effects (e.g., fails if ID not found), permissions, or idempotency. Minimal but not contradictory.

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?

Two concise sentences with no filler. Front-loaded with verb and resource, then lists fields and behavior.

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?

No output schema; description does not mention return value (e.g., updated object). Required ID is in schema. Reasonably complete for a simple CRUD update, but could disclose error conditions or permissions.

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 coverage is 100%, so parameters are well documented. Description reiterates field groups but adds little beyond schema (e.g., no value constraints or usage tips). Baseline 3 is appropriate.

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?

Description clearly states it updates an existing client and lists the updatable fields (name, active status, address, currency). Distinguishes from get_client (read) and create_client (creation).

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?

Implicitly indicates when to use (when modifying a client), and notes partial update behavior ('Only provided fields will be updated'). No explicit when-not or alternatives, but sufficient for a typical update tool.

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