google_set_account_alias

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

With no annotations, the description carries the full burden. It discloses the key behavior that the alias can replace account IDs universally and that an empty string removes the alias. It does not mention edge cases like case sensitivity or persistence, but these are minor for a simple setter.

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, efficient and front-loaded. The first sentence states the purpose, the second explains the broader utility and removal semantics. No wasted words.

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 is complete enough: it covers the action, the alias usage in all tool calls, and removal. The schema handles parameter details, so the description does not need to over-explain.

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 schema already documents both parameters with clear descriptions, achieving 100% coverage. The description adds value by giving a concrete example and restating the removal behavior, but it does not add substantial meaning beyond the schema.

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 action ('Set a friendly alias') and the resource ('on a Google account'), with concrete examples. It distinguishes itself from sibling tools like google_set_account_labels and google_set_account_description by focusing specifically on aliases.

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 when to use this tool: to create a reusable alias that can substitute for the account ID in all tool calls. It does not explicitly mention alternatives or exclusions, but the context is clear enough for the agent to select it appropriately among similar account-setting tools.

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