list_firestore_databases

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

No annotations are provided, and the description does not disclose any behavioral aspects beyond the listing action itself. It fails to explicitly state that the operation is read-only or mention permission requirements, side effects, or potential limitations.

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 fairly concise and structured with Description, Args, and Returns sections. However, the Returns section redundantly repeats the main description ('List of Firestore databases in the specified GCP project'), which prevents a perfect score.

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 one-parameter list tool, the description is minimally adequate but does not describe the return format (e.g., database names, metadata, or complete resource objects). With no output schema, more detail about the returned list would improve 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?

The Args section clarifies that project_id is the ID of the GCP project to list Firestore databases for, adding semantic meaning not present in the schema. Since schema_description_coverage is 0%, this parameter explanation is essential and informative.

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 'List Firestore databases in a GCP project' with a specific verb and resource. It distinguishes itself from sibling tools like list_databases by explicitly naming Firestore.

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 no guidance on when to use this tool versus alternatives such as list_databases or list_firestore_collections. It merely restates the function without context or exclusions.

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