Create, rename or remove a bookmark folder

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

Annotations already declare destructiveHint=true, but the description adds genuinely additive context beyond them: the blast radius of removal (children are deleted too), the well-known root GUIDs used to address toolbar/menu/unfiled/root, and the backing API surface. It does not cover permissions or what the list action returns, so not a 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?

Three tight sentences, front-loaded with the resource and the sibling differentiation, then the safety caveat. The 'MEASURED:' prefix is terse internal jargon that costs a little readability but every sentence carries information.

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 4-parameter mutation tool with full schema coverage, no output schema, and annotations already flagging destructiveness, the description supplies the missing pieces: scope vs siblings, destruction of children, and root GUID addressing. Only the shape of the 'list' response is left unstated, which is a minor gap given there is no output schema.

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 baseline is 3; the description earns above that by explaining that root folders are addressed by fixed GUIDs (toolbar____, menu________, etc.), which materially changes how an agent supplies the `guid` and `parent` parameters, and by tying `action:"list"` to the child-count check.

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 the resource precisely ('bookmark FOLDERS') and explicitly distinguishes itself from the sibling bookmark tools that 'only handle individual bookmarks', which is the key disambiguation an agent needs. The verb is generic ('Manage') and the concrete actions (create/rename/remove/list) live in the title and the action enum rather than the description body, keeping it just short of a 5.

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 a concrete pre-condition for destructive use: 'Removing a folder removes its contents, so check the child count first with action:"list"' — that is real when-to-do-what guidance including a recommended tool sequence. It also implicitly scopes the tool against the individual-bookmark siblings, though it does not address the other folder-capable sibling (browser_bookmark_manage).

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