wealthbox.contacts.update

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

No annotations are present, so the description must disclose behavior. It only mentions the need for id and changed fields and the option to pass a raw body, without explaining update semantics (partial vs full replacement), response structure, or side effects. This is insufficient for a mutating 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 three short sentences, with the purpose stated first. Every sentence adds some guidance, with no redundant content.

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?

The tool has 9 parameters including nested objects and no output schema, yet the description provides only minimal invocation guidance. It lacks details about response format, error handling, and the interaction between 'body' and the structured fields, making it incomplete for complex usage.

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 0%, so the description must compensate. It identifies the required 'id' and the concept of 'changed fields', and notes the 'raw body' option, but doesn't explain individual parameters like type or the structure of emails/phones/addresses beyond schema names.

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 states 'Update contact' which clearly identifies the action and resource, distinguishing it from sibling tools like create, get, and delete. It also specifies that an id is required, reinforcing the update semantics.

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 instructs to 'Provide id and changed fields', establishing when to use the tool (existing contact, modification). It doesn't explicitly mention alternatives or exclusions, but the context is clear for an update operation.

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