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

Annotations already declare this as a non-read-only, idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description adds a genuinely non-obvious side effect not present in the annotations: the folder is created when no folder has that name, and matching is case-insensitive. It does not say what happens if both parameters are supplied or if uncategorized=true is used on an already-uncategorized flow.

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 compact sentences with no filler: the primary action and its side effect come first, then the parameter constraint. Every clause carries distinct information and nothing repeats the schema verbatim.

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 three-parameter mutation tool with no output schema and full annotation coverage, the description supplies the essential elements: the action, both modes, the side effect of folder creation, and the exclusivity rule. Minor gaps remain around error behavior for conflicting or redundant parameters, but nothing critical is missing.

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 coverage is 100%, so the baseline is 3, but the description contributes real meaning the schema lacks: the mutual-exclusivity constraint between folderName and uncategorized, which is not expressed as anyOf/oneOf in the schema. That constraint is the single most important thing an agent must get right when calling this tool, so it deserves credit above baseline.

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 and resource ('Move a flow into a folder') and immediately covers both operation modes, including the non-obvious behavior that a missing folder is created. An agent can distinguish this from sibling tools like ap_create_folder or ap_list_folders without opening a schema.

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 sentence 'Pass exactly one of folderName or uncategorized' gives an explicit, actionable usage rule that maps each mode to its purpose, and 'take it out of its folder with uncategorized=true' clarifies the second mode's intent. It stops short of naming a sibling alternative (e.g. ap_create_folder) for agents that only want folder management, so it is clear context rather than full routing guidance.

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