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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful context that the tool 'opens nothing by itself' and returns step-by-step instructions rather than performing actions. It does not describe the exact output format or what a 'step by step' response contains beyond screens, buttons, and fields.

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 spends a full sentence on Formstack's V2025 API release date and the absence of an MCP server, which is irrelevant to invoking this tool. That trivia interrupts the core message and makes the definition longer without helping the agent act. The useful parts are buried after a misleading opening.

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 guide-style tool with no parameters and no output schema, the description explains the intended next step with cotlet_browser_* tools. But it does not clarify what the returned guide contains beyond a generic list of screens, buttons, and fields, and the misleading name/title leaves ambiguity about whether any actual form data is returned.

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?

The tool has zero parameters, so there is no parameter meaning to add. The schema is empty and additionalProperties is false, consistent with the description. The baseline of 4 for a zero-parameter tool 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?

The name and title promise 'List forms,' but the description says the tool 'Returns how to do it in Formstack step by step' and 'opens nothing by itself.' That is a guide-producing tool, not a form-listing tool, so an agent expecting actual form data will be misled. It does eventually clarify its real function, but the first sentence reinforces the wrong expectation.

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?

The description says to use this tool first and then execute the steps with cotlet_browser_* tools in the user's Formstack Cloud Browser. That gives a clear intended workflow. However, it does not say when not to use this tool or name an alternative for actually retrieving form data, leaving the agent to infer the boundary.

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