Reorder dialog folders

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

Annotations already declare openWorldHint and idempotentHint. The description adds the core behavior of setting display order, but does not disclose edge cases like whether all folder IDs must be included, how invalid IDs are handled, or the effect on unsaved orders. No contradiction with annotations.

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 description is a single, concise sentence that front-loads the action and key input. No redundant or unnecessary information is present.

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?

The tool is simple, but the description lacks details on accountId usage, return behavior, or whether the order list must replace all folders or can be partial. Given no output schema and limited annotations, the description is adequate but leaves open common edge cases.

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 0%, so the description must compensate. It implicitly explains the required 'order' parameter as a list of folder IDs in desired sequence, but does not mention the optional 'accountId' parameter or its purpose. This partial compensation supports a mid-range score.

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 clearly states the verb 'Set' and the resource 'display order of folders', while specifying the exact input ('list of ids in the desired sequence'). It distinguishes this from sibling tools like edit_folder or create_folder by focusing specifically on ordering.

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 provides clear context on what the tool does and how to invoke it, but does not explicitly mention when to prefer it over alternatives or any exclusions. The 'desired sequence' wording makes usage intuitive, but no explicit when-not-to-use guidance is given.

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