firestore-transaction

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'transaction with read and write operations,' which implies atomicity and potential data mutation, but fails to disclose critical traits: whether it requires specific permissions, how errors are handled, if there are rate limits, transaction isolation levels, or what happens on failure (e.g., rollback). For a complex mutation tool with no annotations, this is a significant gap in transparency.

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 with zero waste—'Execute a transaction with read and write operations.' It is appropriately sized and front-loaded, directly stating the core functionality without unnecessary elaboration. Every word earns its place, making it highly concise and well-structured.

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 a transaction tool (involving multiple parameters, mutation operations, and no output schema), the description is incomplete. It lacks details on behavioral aspects like error handling, atomicity guarantees, and response format. With no annotations and no output schema, the description should provide more context to help the agent understand how to use it effectively and what to expect, but it falls short.

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 clear descriptions for 'reads,' 'operations,' and 'conditionScript.' The description adds no additional parameter semantics beyond what the schema provides—it doesn't explain the relationship between reads and operations, the format of document paths, or the purpose of the conditionScript. Given the high schema coverage, the baseline score of 3 is appropriate, as the 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 ('Execute') and resource ('a transaction with read and write operations'), making the purpose understandable. However, it doesn't explicitly distinguish this from sibling tools like firestore-batch-write or firestore-field-value-batch, which might also handle multiple operations. The description is specific about transaction semantics but could better differentiate from batch operations.

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 many sibling tools for individual operations (e.g., firestore-create-document, firestore-update-document) and batch operations (e.g., firestore-batch-write), the agent receives no explicit direction on when this transaction tool is preferred—such as for atomicity, consistency, or conditional execution based on read data. Usage is implied but not stated.

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