Gbp.Accounts.List

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

With no annotations, the description carries the full burden; it does add real value by disclosing the access-scoping rule ('the authenticated user can access'), which tells the agent results are permission-filtered and no identifier parameter is needed. However, it says nothing about pagination/page size, rate limits, or ordering, which matters for a list endpoint with no parameters.

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?

A single front-loaded sentence of roughly a dozen words with zero filler. Every element (verb, resource, permission scope) 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 zero-parameter read-only listing with an output schema that documents the return shape, the description covers what is enumerated and who can see it. The only meaningful gap is pagination behavior, which is not disclosed anywhere visible in the definition.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. Nothing in the description contradicts or omits parameter-level 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 a specific resource ('Google Business Profile accounts') with a clear scope ('the authenticated user can access'). No sibling in the GBP namespace lists accounts, so there is no real ambiguity, but the description offers no explicit sibling differentiation (e.g., that locations are listed separately via gbp.locations.list).

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?

Usage is only implied: the name and verb make it obvious this is the entry point for enumerating accounts. There is no explicit statement of when to use it versus alternatives, and no mention that this is typically the first call before gbp.locations.list or gbp.location.get within the account hierarchy.

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