Update client

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

The description adds context about the param structure (fields inside params, using documented field names) beyond the annotations. Annotations already indicate it is destructive (destructiveHint: true), and the description aligns with that. It does not contradict annotations.

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 sentences, front-loaded with the purpose and then providing essential param guidance. No wasted words.

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 mutation tool with nested params and no output schema, the description covers the key aspects: target identification (uuid), param structure, and field naming convention. It lacks explicit mention of return values or side effects, but annotations cover destructive behavior and the openWorldHint adds context.

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 50%; uuid lacks description but params has one. The tool description adds the key detail that params uses '_1/_2' field names from docs, partially compensating for the missing schema descriptions. However, it does not elaborate on all possible fields or the uuid parameter semantics.

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 updates an existing client by uuid, using a specific verb and resource that distinguishes it from sibling tools like create_client, delete_client, and get_client. The scope is precise.

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 implies this is for modifying an existing client, which differentiates it from creating or deleting. It also provides guidance on how to structure params with '_1/_2' borrower field names, but it does not explicitly mention when not to use it or name alternative tools.

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