ff list forms

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds material context beyond them: the required access scope and the fact that this returns a single page rather than a complete snapshot. It stops short of describing pagination mechanics or return shape.

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, front-loaded sentences with no filler: scope first, precondition second, boundary third. Every sentence adds a distinct fact.

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 nine-parameter read tool with 11% schema coverage and no output schema, the description is too thin: most parameters are undocumented in both places, and there is no guidance on pagination, result size, or how the date/sort filters compose. Auth and scope are covered well, but the parameter surface is largely left to inference.

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 only 11% (just 'account'), and nine parameters exist, so the description carries the compensation burden. Its phrase 'native sorting and date filters' loosely gestures at sort_by/sort_column and date_range/filter_by but explains nothing about page, per_page, search, status, or the ASC/DESC enum.

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 ('Read one Forms page') and bounds the scope with 'Not an all-forms snapshot,' which implicitly separates it from a full-listing or single-form tool. It does not name ff_get_form or any sibling explicitly, so the differentiation is by inference rather than declaration.

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 a real precondition ('Requires fluentform_dashboard_access and applicable native form permissions') that tells the agent when it can be called, and the 'not an all-forms snapshot' note hints at scope limits. There is no explicit when-not or named alternative that the agent should use instead for a full listing.

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