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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no pagination behavior, no scope of folders returned, no auth context. With the lower bar set by annotations, it still contributes zero behavioral context.

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 text is short, but its brevity stems from under-specification rather than disciplined editing. There is a single fragment with no front-loaded scope or detail to justify it.

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?

An output schema exists, so return values need not be explained, which keeps the complexity low. Even so, for a paginated list tool with three fully undocumented parameters and no sibling differentiation, the description is too thin for an agent to call it confidently.

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?

Three parameters (limit, cursor, connection_context) exist with 0% schema description coverage, and the description mentions none of them. Both the schema and the description leave limit bounds, cursor mechanics, and the connection_context pattern format entirely undocumented.

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 'List creative folders' is essentially a restatement of the tool name, which already encodes verb (list) and resource (creative folders). It offers no additional distinguishing information against close siblings such as creatives_list, creatives_list_cloud, or creatives_create_folder, so an agent gains nothing from reading it.

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?

There is no guidance on when to use this tool versus creatives_list or creatives_list_cloud, no mention of prerequisites, and no exclusions. The purpose is loosely inferable from the name alone, but the description supplies no routing logic.

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