List account databases

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results are paginated, which is useful, but it does not disclose default page sizes, ordering, or what fields are returned. No contradiction with annotations.

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 deliver the core purpose and the most important filtering use case with no filler. The primary action is front-loaded and each sentence 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 read-only list endpoint with full schema descriptions and annotations, the description is sufficiently complete: it states pagination, account scope, and the key filter combination. The lack of an output schema is mitigated by the straightforward nature of the tool, though return field details would add further completeness.

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 100%, so the description does not need to re-document parameters. It does add a small amount of intent by explaining that domain and is_assigned filters are used to find databases assigned to a specific domain, but this largely mirrors the schema descriptions.

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 returns a paginated list of databases for a specified account, and the title reinforces the account-level scope. It is distinguishable from create/delete database siblings, though it does not explicitly contrast with website-level database listing tools.

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 gives concrete guidance on using the domain and is_assigned filters together to find databases assigned to a domain. However, it does not state when to prefer this tool over alternatives such as agency-hosting_listWebsiteDatabasesV1 or list database tools for other scopes.

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