updateLeadProperty

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

No annotations are provided, so the description must convey behavioral details. It only states 'update' without disclosing whether the operation is additive, overwriting, or requires specific permissions. No mention of side effects or error conditions.

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?

While the description is short (one sentence), it is under-specified rather than concise. It sacrifices necessary detail for brevity, resulting in a lack of useful information.

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?

Given the complexity (10 parameters, no output schema, no annotations), the description is severely incomplete. It fails to explain return values, which fields are updated, validation rules, or any behavioral 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?

With 10% schema description coverage (only leadId has a description), the description adds no meaning beyond the schema. It does not explain what each property parameter represents or how they relate to the lead's property.

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 the verb ('Update') and the resource ('lead's current property information'), distinguishing it broadly from sibling tools like updateLead and updateLeadInquiry. However, it lacks specificity that would differentiate it from these related tools.

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?

No guidance on when to use this tool versus alternatives like updateLead or updateLeadInquiry. The description does not mention prerequisites, typical use cases, or constraints.

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