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

Annotations already declare a safe read operation (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description earns real credit by disclosing a non-obvious constraint: query results are capped at `limit` with a truthful hasMore but cannot be paginated further, while cursor pagination only works on the unfiltered path. Auth needs and rate limits remain unstated.

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?

Front-loads the core purpose and packs three distinct behavioral clauses into a few sentences, all of which carry information. The trailing sentence about forms created via request_create carrying origin 'inline' is tangential and mildly confusing in context.

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?

With no output schema, the description carries return-value burden; it covers the critical pagination contract (hasMore, nextCursor, cap on filtered search) but never describes what a returned form object contains or result ordering. Complete on the behavioral pitfalls, incomplete on payload shape.

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 80%, so the baseline is 3. The description largely restates folderId and query semantics, but adds genuine value by describing the interaction between `query` and `cursor` (mutually exclusive pagination paths) that the schema does not capture.

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 and resource ('List forms') scoped to a workspace, and immediately characterizes the two optional filter modes. Against a large sibling set that includes form_get and fields_list, an agent can tell this is the collection-listing operation without opening the 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?

Gives concrete operational guidance: folderId=null means root-only, omit for all, and explains when to use `query` versus `cursor`. It does not explicitly name sibling alternatives (e.g., form_get for a single form), but the routing conditions for its own two modes are clear.

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