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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds the assignment side effect but does not disclose what an update overwrites, whether omitted fields are cleared, or how clear_description/remove_funnel_assignment interact with the update. It is consistent with annotations but adds limited behavioral context beyond them.

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 a single sentence with no filler, front-loading the core operation, the resource, and the optional behavior. Every phrase earns its place.

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 rich input schema and output schema cover parameter meaning and return value shape, and annotations cover the destructive nature. However, for a create-or-update tool with 11 parameters and zero required fields, the description could clarify update semantics (what is replaced vs preserved) and the effect of the clear_description and remove_funnel_assignment flags, rather than leaving that entirely to schema property descriptions.

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%, so each parameter is already documented in the input schema. The description mentions funnel and step assignment, which maps to assign_to_funnel and assign_to_funnel_step, but it does not add meaning beyond what the schema already provides, so the baseline of 3 applies.

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 uses specific verbs ('create or update') and names a concrete resource ('Chasync lead capture form'), then adds a distinguishing behavior: optionally assigning submissions to a funnel and step. This is enough to separate it from sibling save_email_template, save_funnel, and save_lead 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?

The phrase 'create or update' clearly implies two usage modes: omit _id to create, provide _id to update, and the optional funnel/step assignment states a likely reason to call the tool. However, there is no explicit when-to-use vs alternatives or exclusions, so the guidance is implied rather than stated.

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