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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuine scope context beyond that: this is a read-only enumeration and folder mutation lives outside the toolset. It does not discuss result size, ordering, or account scoping nuances, so the added value is modest.

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 tight sentences with zero filler, and the core enumeration plus its purpose is front-loaded before the scope caveat about dashboard-managed folders.

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?

With no input parameters, full annotation coverage, and a declared output schema, nothing further is required. The description supplies exactly the missing pieces an agent needs: why the output matters and where folder management actually happens.

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, so the baseline is 4. The description does useful adjacent work by explaining what the returned folder path is for (the publish `folder` argument), which frames how the output is consumed.

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 ("Lists the folders on this account") and immediately adds the payload's purpose: each folder comes with the path that a publish's `folder` argument accepts. It also distinguishes itself from absent siblings by declaring no tool here creates a folder, so an agent will not hunt for a create_folders tool.

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 makes the use case clear (you need this to obtain valid `folder` values before publishing) and closes off a dead end by saying folders are created and rearranged in the dashboard. It stops short of naming a specific sibling such as publish_files as the follow-up call, so a 4 rather than a 5.

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