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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the description's main added value is the 'Cloud must be enabled' precondition. It says nothing about what happens when Cloud is disabled (error vs empty list) or about the shape/volume of the returned schema listing, though the output schema covers return structure.

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 short sentences, zero filler, with the operation stated first and the precondition second. Everything present 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, single-parameter listing tool with a full output schema, the description covers purpose and the key precondition. The remaining gap is error behavior when Cloud is not enabled, which would help an agent decide whether to call projects_cloud_enable first.

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 description coverage is 100% for the single project_id parameter, and the description does not add format or constraint detail beyond it. With the schema carrying the parameter semantics, baseline 3 applies.

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 states a specific verb and resource (list Postgres schemas and tables) scoped to the project's Cloud database, which distinguishes it implicitly from row-level siblings such as projects_cloud_database_rows and projects_cloud_database_query. It stops short of naming an alternative sibling outright, so it is clear but not maximally differentiated.

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 only usage guidance is the prerequisite 'Cloud must be enabled', which tells the agent a precondition but not when to pick this tool over projects_cloud_database_schema_create or projects_cloud_database_rows. There is no explicit when-not-to-use or alternative routing.

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