gorelo_list_forms

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the default ordering behavior ("most recently updated first"), which is useful context, but it omits meaningful behavioral facts such as the default exclusion of archived forms, which only appears in the schema.

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 with no filler. It is efficient, though it is arguably too terse for a nine-parameter filtered list tool.

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?

The rich schema compensates for most of the description's thinness, and no output schema exists to explain. Still, for a tool with nine filters, cursor pagination, and a non-obvious archived-exclusion default, the one-line description leaves the agent to reconstruct the intended workflow from the schema alone.

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 one of the nine parameters is already documented, including the archived-default and pageSize rejection rules. The description adds no parameter-level meaning beyond the ordering note, so the baseline 3 applies.

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 ("Lists the service provider's forms") plus the default ordering, so an agent knows exactly what it retrieves. It does not differentiate from close siblings such as gorelo_list_form_responses or gorelo_create_form_submission_link, which an agent must infer.

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 on when to use this versus gorelo_list_form_responses or any other listing tool, and no mention of prerequisites or when to page. The purpose implies a listing use case, but nothing in the text routes the agent among alternatives.

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