cloak_persistent_profile_create

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the directory location and the word "fresh," but is silent on the critical case of a duplicate name (error vs overwrite), permissions required, and whether the operation is reversible. For a creation/mutation tool this is a notable gap.

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, front-loaded sentences with no wasted words. The primary action is stated first, with the follow-up usage note second.

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?

With no output schema, the description would need to explain the return value, and with no annotations it should cover the safety/error profile. It covers the essential location and workflow but leaves the duplicate-name outcome and return value unstated, making it only adequately complete.

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 partially does by showing <name> is interpolated into the profile path, but it does not explain the allowed character set (the schema pattern does that) or constraints on the name. Only partial compensation.

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 (create) and resource (persistent profile directory) with the exact target path, so the agent knows precisely what the tool produces. It does not explicitly distinguish from the sibling list/delete tools, but the verb makes the distinction reasonably clear.

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 second sentence ("Use as --profile-dir on next launch") hints at the intended workflow, implying the tool is a prerequisite before launching a persistent session. However, it says nothing about when to prefer this over alternatives or what happens if a profile of the same name already exists.

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