firestore-get-collection-by-path

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

No annotations are provided, so the description carries full burden. It states it 'Get documents' but doesn't disclose behavioral traits like whether this is a read-only operation (implied but not explicit), what permissions are needed, how many documents are returned (all vs paginated), error handling for invalid paths, or response format. For a retrieval tool with zero annotation coverage, this lacks critical operational context.

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, efficient sentence that front-loads the core action ('Get documents from a collection') and adds qualifying details ('using full path', 'supports subcollections') without waste. Every word earns its place, making it easy to parse quickly.

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 moderate complexity (retrieving documents from potentially nested collections), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the return value looks like (e.g., array of documents, metadata), handling of large collections, authentication requirements, or error scenarios. For a read operation in a database context, this leaves significant gaps for an agent to use it correctly.

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%, with the single parameter 'collectionPath' fully documented in the schema as 'Full path to the collection (e.g., 'users/userId1/orders')'. The description adds minimal value beyond this, mentioning 'full path' and 'supports subcollections' which aligns with but doesn't expand on the schema's example. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Get' and resource 'documents from a collection', specifying it uses a 'full path' and 'supports subcollections'. This distinguishes it from simpler collection retrieval tools like 'firestore-get-collection' that might not handle subcollections. However, it doesn't explicitly differentiate from 'firestore-query-collection-by-path' which might offer more filtering capabilities.

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 like 'firestore-get-collection' (which might use simpler paths) or 'firestore-query-collection-by-path' (which might offer query capabilities). It mentions 'supports subcollections' but doesn't clarify if this is unique or when subcollection paths are required versus other approaches.

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