bookmarks_create_folder

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

No annotations are provided, so the description carries the full burden for a mutation tool. It adds genuinely useful non-schema context — the profile-scoping rule and where to get profile_id — but says nothing about duplicate titles, permission failures, or whether the call returns the new folder's ID, all of which matter for a create operation.

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 short sentences, front-loaded with the action, then the mandatory prerequisite. No filler or restated boilerplate; the only small inefficiency is the line break separating the two ideas rather than integrating them.

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 described, and all three parameters are covered between schema and prose. What's missing is failure behavior (duplicate title, invalid parent) — relevant but not blocking for an agent to call this correctly.

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 coverage is 67% and the uncovered parameter is exactly the one the description addresses: profile_id has no schema description, and the prose explains how to obtain it and that IDs are profile-local. The parent_id type restriction is already fully documented in the schema, so the description doesn't duplicate it.

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: 'Create a new bookmark folder.' The resource noun ('bookmark folder') separates it from bookmarks_create, which plainly creates a bookmark rather than a container. It stops short of explicitly naming that sibling, so an agent must infer the distinction from the names.

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 clear prerequisite chain ('profile_id is required: obtain it from profiles_list') and a hard constraint ('never reuse IDs in another profile'). It never says when to use this versus bookmarks_create or when nesting via parent_id is appropriate, so the selection guidance is implied rather than stated.

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