crm_update_leadPatch lead attributes (name, company, title, email, LinkedIn, phone, notes, tags, deal value + currency). Stage and owner have their own tools (crm_move_lead, reassign_crm_lead). Reversible.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| tags | No | Replaces the tag list | |
| No | |||
| notes | No | ||
| phone | No | ||
| title | No | ||
| currency | No | ISO code, e.g. USD | |
| last_name | No | ||
| deal_value | No | ||
| first_name | No | ||
| company_name | No | ||
| linkedin_url | No | Full http(s) URL |
Changes observed during successful MCP inspections.
Input schema / properties / currencyAdded value: +{
+ "description": "ISO code, e.g. USD",
+ "maxLength": 3,
+ "type": "string"
+}Input schema / properties / linkedin_urlAdded value: +{
+ "description": "Full http(s) URL",
+ "type": "string"
+}Input schema / properties / tagsAdded value: +{
+ "description": "Replaces the tag list",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. 'Patch' usefully signals partial-update semantics and 'Reversible' discloses the safety profile, which is real added value. However it omits permission requirements, what happens to unspecified fields, and the response shape, leaving meaningful gaps 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?
Two tight sentences, front-loaded with the field scope before the sibling exclusions. 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 12-parameter mutation tool with no annotations and no output schema, the description covers scope, partial-update intent, and reversibility but leaves auth, unspecified-field behavior, and return values unaddressed. Adequate but with clear gaps given the complexity.
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 only 25%, and the description compensates by mapping its field list (name, company, title, email, LinkedIn, phone, notes, tags, deal value, currency) onto the parameters. Still, it adds no format guidance for fields like currency or linkedin_url, and mapping the names is largely redundant with the schema properties themselves.
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?
States a specific verb (patch/update) and resource (lead), enumerates exactly which attributes are covered, and explicitly names the two fields (stage, owner) handled by sibling tools crm_move_lead and reassign_crm_lead. An agent can distinguish this from reassign_crm_lead and crm_move_lead without opening any schema.
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?
Clears the main routing ambiguity by directing stage changes to crm_move_lead and owner changes to reassign_crm_lead, implicitly scoping this tool to those fields. It stops short of stating prerequisites or when-not-to-use beyond the two exclusions, so not a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.