auth_clear_cloak

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

No annotations are provided, so the description carries the burden. It discloses that the operation clears auth state and requires confirmation (confirm=true), which implies a destructive, safety-gated action. However, it does not mention reversibility, side effects, or permissions, leaving some gaps.

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?

The description is one sentence plus a short requirement note. It is front-loaded with the action and contains no wasted words, earning full marks for conciseness.

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?

The tool has three required parameters, no annotations, and no output schema, yet the description provides only minimal context. It does not explain the effect of 'confirm', potential consequences, or how it fits with sibling tools, leaving the agent with an incomplete picture.

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%, and the description does not explain the parameters directly. It vaguely mentions 'site' and 'profile' but does not map site_id, target_profile, or confirm to their roles or formats. The parameter names are somewhat self-explanatory, but the description adds little value beyond that.

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?

The description clearly states the action ('Clear'), the resource ('authentication state'), and the scope ('one registered site' from a 'Cloak profile'). It distinguishes this from sibling tools like auth_list_sites (listing), auth_sync_to_cloak (syncing), and auth_verify_cloak (verifying).

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 description implies when to use the tool (when clearing a site's auth state from a Cloak profile) but does not explicitly state when not to use it or mention alternatives among sibling tools. The 'Requires confirm=true' note gives a prerequisite but not usage context.

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