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

Annotations are thin (only destructiveHint=true), so the description carries most of the load. It maps the operation to the API endpoint ("Formstack: POST /folders") and explains root vs nested placement, but says nothing about auth needs, duplicate-name behavior, or side effects of folder creation.

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?

One compact sentence plus a short endpoint tag; the core action is front-loaded and nothing is wasted.

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 two-parameter creation tool with no output schema and full schema coverage, the description covers what an agent needs to call it correctly. Minor gaps remain around failure/duplicate handling.

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%, and the schema already documents both `name` and `parent` (including "omit for root level"). The description merely restates the root/parent distinction, so baseline 3 applies with no added syntax or format detail.

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+resource ("Create a folder for organising forms") and adds the scope of where it can be created. It is implicitly distinguishable from siblings like formstack_get_folder and formstack_list_folders, though it never names them.

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 mention of "at the root or inside a parent folder" gives useful placement context, but there is no explicit when-to-use versus alternatives and no prerequisites or permission requirements stated.

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