mautic_list_forms

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only "GET /api/forms", which restates the endpoint rather than disclosing behavior such as page-size capping by MAUTIC_MAX_LIMIT, pagination semantics, or whether all forms are returned by default.

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 text is front-loaded and contains zero filler, but it is terse to the point of under-specification — the second sentence adds almost no decision-relevant information beyond the endpoint path.

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 six optional parameters, partial schema coverage and no output schema, the description should explain what a listing call returns and how limit/start/search interact. Instead it offers a two-word summary that leaves the agent guessing about default result size and filtering behavior.

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?

Only 50% of the six parameters carry schema descriptions, and three (minimal, orderBy, orderByDir) have none at all. The description compensates for none of this — it never mentions filtering by search string, sort order, or the minimal flag that presumably trims the payload.

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?

"List forms" names a specific verb and resource, so the basic action is unambiguous. However, it gives no scope information (all forms? paginated? filterable?) and does nothing to separate it from siblings such as mautic_get_form (single form) or mautic_list_form_submissions.

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?

There is no when-to-use guidance at all: no mention of when to prefer mautic_get_form for a specific form, no prerequisites, and no note about how the search/orderBy parameters change the query. Usage is only implied by the word "List".

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