Start Gmail login (opens browser)

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

With no annotations, the description fairly discloses the open-browser behavior and the need for user approval. It doesn't mention any destructive actions or permissions, but for an auth initialization tool, this is adequate.

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 front-load the purpose, provide usage examples, and state next steps. No fluff; every word earns its place.

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 simple two-parameter tool with no output schema, the description covers the core workflow effectively. The only missing piece is the 'chatScope' parameter, but overall it's sufficient for correct agent invocation.

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 description adds meaning to the 'command' parameter via examples (e.g., 'you@example.com personal'), but does not explain the 'chatScope' parameter at all. Schema coverage is 0%, so description partially compensates but leaves a 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?

The description clearly states it starts Gmail login, provides example commands, and distinguishes from siblings like connect_finish. The verb 'connect' is specific to initiating authentication.

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 tells when to use (to start login) and the immediate next step (run connect_finish). It implies a workflow but doesn't specify when not to use or alternatives.

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