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

Annotations already declare destructiveHint=true, but the description adds substantive context beyond them: deletion cascades to all quizzes and respondent answers, non-empty deletion requires the confirm_delete_quizzes flag, and the default folder is protected. It does not mention required permissions/roles for management, so not a full 5.

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?

Front-loaded with the action set and immediately followed by the highest-risk consequence (cascading delete). Dense and largely waste-free, though the confirm/default-folder clauses could be slightly tighter.

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?

No output schema exists, and the description covers the dangerous behavior and a resource pointer so an agent can call it safely. Gaps remain on reorder semantics and required permissions, but the critical destructive path is fully explained.

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%, so the schema already documents all six parameters including the action enum and the confirm_delete_quizzes guard. The description reinforces the delete precondition but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 cluster (renames/deletes/reorders account folders) and the three discrete actions are enumerated. An agent can separate it from siblings like create_folder (creates), get_folder_list (reads), and manage_folder_access (permissions) without opening the 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?

Gives clear conditional guidance: a non-empty folder is deleted only with confirm_delete_quizzes, and the default folder cannot be deleted. It also routes to the folder://list resource. It stops short of naming explicit alternatives for the rename/reorder cases, so no exclusions/alternatives tier, but the when-conditions are concrete.

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