hosting_listAccountDatabasesV1

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

The description mentions pagination and filters but does not disclose behavioral traits like read-only nature, rate limits, or authentication requirements. Since no annotations are present, the description carries the full burden, which is only partly fulfilled.

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?

The description is two sentences long, front-loaded with the main purpose, and includes a concise usage tip. No unnecessary 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?

Given the tool's simplicity and complete schema descriptions, the description covers the essential purpose and a key use case. It lacks details about return structure (e.g., fields in each database object), but the pagination mention partially compensates. A more complete description would include this, but it's adequate.

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 baseline is 3. The description adds context for domain and is_assigned filters by explaining their combined use, but other parameters like username, page, per_page, and search are not elaborated 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 tool returns a paginated list of databases for a specified account, using a specific verb and resource. It distinguishes from sibling listing tools by focusing on databases.

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 provides guidance on using domain and is_assigned filters to find databases assigned to a domain. However, it does not explicitly state when not to use this tool or compare with alternatives.

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