firestore_list_collections

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

No annotations are provided, so the description carries full responsibility. 'List' implies a read-only operation, and 'from Firestore emulator' provides context about the environment. However, it does not disclose return format (e.g., array of strings), potential absence of collections, or any edge cases. This is adequate for a simple read tool but not maximally transparent.

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 a single sentence that front-loads the action and resource, with zero wasted words. It is perfectly sized for the simplicity of the tool.

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 low complexity (no params, no output schema), the description provides the essential context: it lists root-level collection IDs specifically in the emulator environment. It is complete enough for an agent to understand the tool's purpose, though it could mention the return type explicitly.

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 tool has 0 parameters, so the schema coverage is trivially 100%. Per the rubric, 0 params earns a baseline of 4. The description adds no parameter info, but none is needed.

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 verb 'List' and the specific resource 'root-level collection IDs from Firestore emulator', distinguishing it from sibling tools like firestore_query (which queries documents) and firestore_get (which retrieves a specific document). The 'root-level' scope adds precision.

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 usage in the context of the Firestore emulator (when you want to see available collections), but it does not explicitly mention when NOT to use it or provide alternatives. It provides clear context but lacks exclusions or comparisons to sibling tools.

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