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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description does add value by naming the returned fields (submission counts, live URL, folder), but it says nothing about pagination behavior or result limits beyond what the schema's page_size default already conveys.

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?

Three short sentences, front-loaded with the resource and the useful return-field summary. The trailing 'Formstack: GET /forms' is a minor redundancy but not enough to hurt readability.

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, describing the returned fields is the right compensation, and pagination is covered by the schema parameters. An agent has what it needs to call this correctly; only pagination/limit semantics are left implicit.

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 every parameter is already documented with type, range and defaults. The description only gestures at filtering and sorting generically, adding no syntax or behavior beyond the schema.

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 ('List') and resource ('forms in the account') plus the useful scope detail that results include submission counts, live URL and folder. It is clearly distinct from the singular formstack_get_form and the sibling list_* tools, though it never names an alternative to route between them.

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?

'Filter by name or folder and sort' implies the supported usage pattern and maps loosely onto the filter/sort parameters, but there is no explicit when-to-use statement or exclusion (e.g. use formstack_get_form when you already have an ID).

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