list_accounts

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

No annotations are supplied, so the description must carry behavioral disclosure. It says the tool lists connected accounts and mentions returned fields, but omits auth requirements, pagination or ordering, whether all accounts are returned, and any read-only safety context. For a no-annotation tool this is thin.

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?

Single front-loaded sentence with no redundant wording. It communicates the resource and the surfaced fields efficiently.

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 zero-parameter list tool with no output schema, the description gives the core resource and fields but does not cover return shape, ordering, or pagination. It is adequate for a simple enumeration but leaves behavioral gaps.

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?

There are zero input parameters, so the baseline is 4. The description's mention of email, alias, and group describes output fields rather than parameters and does not need to add parameter meaning.

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 verb, 'List', and resource, 'connected Gmail accounts', and names the surfaced fields (email, alias, group). The list verb clearly separates it from add_account, assign_account, and remove_account siblings.

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?

Implies usage by naming the resource to enumerate, but gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent can infer it is the read path for accounts, yet the description does not state exclusions or when to prefer another sibling.

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