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

Annotations only supply destructiveHint=true, which is thin and arguably miscalibrated for an additive create operation. The description adds the endpoint (POST /folders) and the root/parent placement model, but says nothing about required permissions, name-collision behavior, or what is returned on success, leaving notable behavioral gaps.

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?

Two short sentences with the core action front-loaded. The trailing 'Formstack: POST /folders' is lean but of limited use to an MCP caller, keeping it just below a perfect score.

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 two-parameter, single-resource creation tool with a fully documented schema, no output schema, and no nesting, the description covers what an agent needs to select and invoke it. The main omission is any hint about the created folder's identity for follow-up calls, but with no output schema that is not strictly required.

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 the schema already documents both 'name' and 'parent' (including 'omit for root level'). The description's phrasing about root vs parent restates that same idea rather than adding syntax, format, or constraint detail, so the baseline of 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?

The description states a specific verb and resource ('Create a folder') plus scope ('at the root or inside a parent folder'), which cleanly separates it from the read-oriented siblings like formstack_get_folder and formstack_list_folders. It stops short of explicitly differentiating itself from other create_* tools, so it lands just under the top band.

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?

Usage is only implied: the mention of root vs parent folder hints at the parent-selection case, but there is no explicit guidance on when to use this instead of, say, creating a folder via other means, nor any prerequisite or conflict conditions. Adequate but with clear gaps.

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