CoDesign Logout

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

The description discloses the full destructive behavior (closing browser, wiping profile) beyond the destructiveHint and idempotentHint annotations. It also reveals that the result includes the target path for verification.

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 sentences, each serving a clear purpose: first states the action, second provides usage instruction and output information. No unnecessary words.

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 is simple with one required parameter, no output schema, and obvious destructive effect. The description covers the action, required input, and part of the output. No gaps.

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?

The schema already describes the confirm parameter as 'Must be true. Wipes the persistent profile.' The description only repeats 'Pass { confirm: true }' and does not add new semantics about the parameter itself. With 100% schema coverage, baseline 3 is appropriate.

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 'Close any running browser and wipe the persistent profile directory', specifying the action and resource. It distinguishes from siblings like codesign_login or get_artboard_image, which are not destructive.

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 instructs to pass { confirm: true } and suggests verifying the target path before re-running. It does not explicitly compare to sibling tools but the context implies usage when ending a session.

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