firestore-get-collection

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get documents' implies a read operation, it doesn't specify important behavioral aspects like whether this retrieves all documents, supports pagination, returns metadata, requires authentication, or has rate limits. For a database operation with no annotation coverage, this leaves significant gaps.

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 extremely concise at just 6 words, front-loading the essential information with zero wasted words. Every word earns its place, making it easy to parse while conveying the core purpose.

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 complexity of Firestore operations and the lack of both annotations and output schema, the description is insufficient. It doesn't explain what 'Get documents' actually returns (documents, metadata, pagination tokens), how it behaves with large collections, or how it differs from similar sibling tools. For a database query tool with no structured safety or output information, this leaves too many questions unanswered.

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 description doesn't add any parameter information beyond what's already in the schema, which has 100% coverage. The schema fully documents the single 'collectionId' parameter, so the baseline score of 3 is appropriate since the schema handles the parameter documentation adequately.

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 action ('Get documents') and resource ('from a Firestore collection'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'firestore-get-collection-by-path' or 'firestore-query-collection', which appear to offer similar functionality with different approaches.

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. With multiple sibling tools that appear related (firestore-get-collection-by-path, firestore-query-collection, firestore-batch-read), there's no indication of when this specific tool is appropriate versus those other options.

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