list_forms

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

There are no annotations, so the description carries the burden of behavioral disclosure. It usefully explains parameter behavior (case-insensitive substring, limit range, default), but it does not state whether the operation is read-only, how results are ordered, or how paging behavior works. 'List' implies read-only, but that is implicit rather than explicit.

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 description is three lines: a one-sentence purpose followed by two concise parameter bullets. Every clause adds information, there is no redundancy, and the most important facts are front-loaded.

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 simple list tool with an output schema and two well-documented optional parameters, the description covers the essential calling information. It lacks usage guidance and explicit behavioral notes like sorting or pagination, but these are minor given the presence of an output schema and the straightforward nature of the operation.

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 0%, so the description must provide semantic meaning for parameters. It fully does: name_contains is described as a case-insensitive substring, and limit is described with a range and default. This adds substantial value beyond the raw type/default information in 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?

The description states a clear verb and resource: 'List forms in the portal.' It is easily distinguished from more specific form tools like get_form and from non-form list tools by the resource namewach, though it does not explicitly contrast itself with those siblings.

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 guidance about when to use this tool versus alternatives such as get_form, list_site_pages, or other list_* tools. The parameters suggest filtering use, but no context, exclusions, or recommended scenarios are provided.

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