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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description does not contradict them. However, it adds no behavioral context beyond 'existing bulk logic'; it doesn't say whether updates replace fields, how conditional params interact, or what side effects occur.

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 only one sentence and avoids filler, but the phrase 'using Chasync's existing bulk logic' is vague and doesn't add useful structure. It is concise at the cost of informative value.

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?

Despite a rich schema and output schema, the tool has 10 params with conditional dependencies and destructive semantics; the description does not explain overall behavior, update semantics, or when to select this tool. An agent would need the schema plus external context to use it correctly.

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 100%, and each parameter explains its role and 'used when update_type is...' conditions. The description itself adds no parameter meaning, so the 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?

The description states the verb 'Update' and resource 'selected leads' with 'bulk' signaling batch scope compared to sibling save_lead. It does not enumerate which update types are supported, but the title and schema fill that in.

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 instead of save_lead or import_leads; there is no mention of prerequisites, limits, or exclusion cases. The plural 'leads' and name imply bulk use, but that is inference rather than instruction.

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