reauthenticate

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

With no annotations, the description carries the full burden, and it explicitly discloses the destructive action ('Deletes the current OAuth token file') and the interactive nature ('triggers the browser authentication flow'). It also notes the logout/login sequence, providing clear behavioral expectations. It could mention side effects or failure modes, but the disclosed information is substantial.

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 three concise sentences, each adding essential information: action, mechanism, and use case. It is front-loaded with the primary purpose and contains no filler or redundant content.

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?

Given the tool's simplicity (0 parameters) and the presence of an output schema, the description is complete enough. It explains the purpose, the destructive side effect, and when to use it, which is sufficient for an agent to decide and invoke the tool correctly.

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 input schema has 0 parameters, so there is no parameter information to clarify. The description adds no parameter details, but none are needed. The baseline for 0 parameters is 4.

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's purpose: 'Perform a logout and new login sequence.' It specifies the mechanism ('Deletes the current OAuth token file and triggers the browser authentication flow') and the use case ('switch to a different Google account'). This distinguishes it from sibling tools, which are all search/analytics related.

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 explicitly says when to use the tool: 'Useful when you need to switch to a different Google account.' It does not provide explicit when-not-to-use guidance or name alternatives, but the use case is clear and the tool is unique among the listed siblings.

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