cloak_persistent_profile_delete

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

With no annotations, the description carries the full burden. It does disclose the destructive action, the confirm safeguard, and the scope caveat that the active session is unaffected. It omits irreversibility, whether it fails if the profile is in use, and the persistence implications of a 'persistent' profile.

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 very short sentences, front-loaded with the action, then precondition, then impact. Every sentence earns its place with no filler.

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 destructive operation with no annotations and no output schema, the description is thin but serviceable: action, precondition, and one scope caveat. It leaves the meaning of 'name' and the failure/consequence behavior (irreversibility, in-use profiles) unaddressed.

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 50%: only 'confirm' is documented in the schema, and the description merely restates 'Requires confirm=true.' The 'name' parameter is undocumented in both schema and description, and it is unclear whether it is a profile name or a directory path. The description does not compensate for the coverage gap.

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: 'Delete a profile directory.' An agent can tell this apart from sibling profile tools (create, list) by the destructive verb. It does not explicitly name alternatives, but the operation is unambiguous.

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?

'Requires confirm=true' gives a clear precondition for invocation, and 'the active session is unaffected' implies when the impact applies. However, there is no guidance on when to choose this over create/list or any exclusion conditions.

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