auto_login

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description adds genuine behavior context beyond them by explaining that enabling causes an expired session to open a browser sign-in and then resume the pending request. It does not say whether the setting persists across sessions or where it is stored, which is the remaining behavioral gap.

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 short sentences, zero waste, with the core action front-loaded and the default surfaced before the explanatory clause.

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 single-boolean toggle with annotations covering the safety profile and no output schema, this is largely sufficient. The only omission worth noting is persistence/auth requirements and the explicit effect of disabling.

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?

Schema coverage is 0%, so the description must carry the meaning of 'enabled'. It does so reasonably by pairing 'on or off' with the concrete effect of 'on' and its default value, though it never states what 'off' means behaviorally (presumably failing instead of prompting).

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?

States a specific action on a specific setting: 'Turn automatic sign-in on or off', with the default noted. The purpose is unambiguous, but it never contrasts itself with the related login or auth_status siblings, so an agent must infer how it differs from them.

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 explains what the on state does but gives no explicit guidance on when to call it versus login or auth_status, nor any precondition. Usage is only implied by the phrase 'automatic sign-in'.

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