Setup Password (Private/Public Gate)

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

Beyond annotations (openWorldHint, destructiveHint), the description adds that it opens a browser window, is one-time setup, and uses PBKDF2-SHA256 hashing. It doesn't mention reversibility or prerequisites, but the added detail is valuable.

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 concise, with three short paragraphs that each add value. It front-loads the main action and uses bullet points for clarity. No wasted sentences, though minor redundancy in explaining the hash.

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 tool with zero parameters and a simple action, the description covers purpose, behavior, and relationship to other tools. It lacks mention of what happens if password already set or if it can be reset, but these are gaps given the existence of an output schema.

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?

No parameters exist, so schema coverage is 100%. The description does not need to add parameter information, and the baseline of 4 applies.

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 tool opens a browser window to set a password for the private/public gate, using specific verb 'open' and resource 'password'. It distinguishes from siblings by noting it's a one-time setup and relates to privacy features like google_make_private and google_unlock.

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 provides context on when to use this tool: it's a one-time setup before marking profiles private. It mentions the result (password storage) and links to related tools, but doesn't explicitly state when not to use it or name alternatives.

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