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

Annotations already cover readOnly, idempotent, and non-destructive behavior, and the description adds the useful scope of 'connected Chasync account' and the 'lead capture' nature of the forms. It does not disclose pagination, defaults for archived/inactive forms, or ordering, but this is a simple list with an output schema and non-conflicting annotations.

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?

A single, front-loaded sentence that conveys the action, object, and scope without filler. Every word earns its place, and there is no repetition of the title beyond what is necessary for precision.

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 read-only list tool with one optional parameter, full schema coverage, and an output schema, the description is largely sufficient. It is only missing light context such as the active-filter option or a pointer to get_form for single-form details, neither of which is critical given the structured fields.

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?

All parameters are documented in the schema; the single optional 'active' parameter already has a clear description ('Filter forms by active status'). The tool description adds no additional parameter meaning, so the baseline of 3 for high schema coverage 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 uses a specific verb ('List') and resource ('lead capture forms'), and scopes it to the connected Chasync account, making the operation clear. It does not explicitly contrast with siblings such as get_form or archive_form, but the list/get/save/archive verbs inherently distinguish it enough to be clear.

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 is given about when to select this tool over list_funnels, list_email_templates, get_form, or archive_form. The description only states what it does, leaving the agent to infer the appropriate context.

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