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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false. The description reinforces this with something the annotations cannot convey: 'returns how to do it ... and opens nothing by itself', which prevents an agent from assuming a side effect occurs. The trailing REST API paragraph adds no behavioral information relevant to invoking the tool.

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 operative sentences are front-loaded and efficient, but the final paragraph about Formstack's V2025 REST API and the 'checked 22 Oct 2026' note is irrelevant to deciding whether or how to call this tool and dilutes the core message.

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 zero-parameter, non-mutating guidance tool with no output schema, the description covers the essentials: it does not act, it returns procedural steps, and the follow-up executor family is named. Only the shape of the returned steps (ordering, granularity) is left unstated, which is minor here.

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 takes zero parameters and the schema is empty with additionalProperties=false, so there is nothing to disambiguate; baseline 4 applies. The description correctly implies no input is needed.

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 names a concrete verb and resource (copy a form in Formstack) and makes the critical clarification that the tool returns step-by-step instructions rather than performing the copy itself. It also points at the executor family (cotlet_browser_*), which separates it from the other formstack_* mutation tools, though it never explicitly contrasts with siblings like formstack_list_forms or formstack_edit_submission.

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?

It gives clear usage context: call this to learn the copy procedure, then carry it out with cotlet_browser_* in the user's Formstack Cloud Browser. There is no explicit when-not or list of alternative formstack_* tools for related form operations, so the guidance is directional but not fully comparative.

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