rtdb_get

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

With no annotations, the description alone establishes that this is a read-only operation targeting the Realtime Database emulator, which are key behavioral traits. However, it omits details on return format, error behavior, or whether the entire subtree is returned, leaving some room for ambiguity.

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, directly front-loaded with the verb and resource. Every word earns its place, with no redundant information or filler.

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 one-parameter read tool with no output schema and no annotations, the description is largely complete. It names the resource (RTDB emulator), the operation (read), and the input (path). The default path is captured in the schema, and the simplicity of the tool reduces the need for extensive detail.

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 schema provides 100% coverage for the single 'path' parameter, including examples and a default value. The description merely repeats 'at a given path' without adding semantic meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb ('Read'), a clear resource ('Realtime Database emulator'), and a scope ('at a given path'), which distinguishes it from sibling tools like firestore_get and auth_get_user. The purpose is unmistakable and immediately actionable.

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 when to use the tool (for reading RTDB emulator data) but does not explicitly contrast it with alternatives such as firestore_get or auth_get_user. No exclusions or when-not-to-use guidance is provided.

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