List website databases

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description goes beyond by disclosing pagination behavior and that returned entries include the database's non-system users, which is not inferable from annotations or schema. It does not add auth or rate-limit context, but that is not required for a read-only list.

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, each with distinct value: first states the operation and scope, second states the key content of the response. No filler or redundancy.

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 read-only, paginated list tool with fully described parameters and read-only annotations, the description is nearly sufficient. It mentions pagination and the notable inclusion of non-system users, though it leaves the full response shape unspecified since there is no output schema. Considering low complexity, this is 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?

All three parameters have schema descriptions (100% coverage), so the baseline is 3. The description's mention of 'paginated list' merely reinforces the schema's 'Page number' and 'Number of items per page' without adding new constraints or format details. website_uid scope is already described in 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?

States a specific verb ('Returns a paginated list'), a concrete resource ('MySQL databases'), and a scoping qualifier ('created for an Agency Plan website'). This distinguishes it from account-level database listing tools such as hosting_listAccountDatabasesV1.

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 implies the tool is for Agency Plan website databases, which differentiates from account-level database tools, but it never explicitly tells an agent when to choose this over a sibling like hosting_listAccountDatabasesV1 or when not to use it. No prerequisites or exclusions are stated.

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