auth_status

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

It provides significant behavioral detail not covered by annotations, specifically stating it 'never shows the token,' and explaining how scope limitations (like missing gmail.modify) impact functional capabilities such as blocking labels and trash.

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 definition is detailed, making it less concise than a short description, but every sentence delivers high-value information necessary for an agent handling complex authentication states.

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 complex, zero-parameter authorization check, the description is highly complete, covering scope validation, reauthentication logic, and security boundaries (never showing the token).

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?

Since the tool has no parameters, the baseline score applies. The description adds no semantic value beyond stating the tool's function regarding scope and status.

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 reports on Gmail sign-in status, covering where tokens are stored, granted scopes, and general validity.

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?

It provides critical usage constraints by defining scenarios (missing or extra scopes) that necessitate user re-authentication, giving the agent clear operational boundaries.

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