list_session_sandbox_databases

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

With no annotations, the description covers behavioral aspects well: it returns a dictionary of sandbox databases, notes they are owned by the current session, and highlights their modifiability. It omits potential permission requirements or performance implications, but for a simple list operation this is sufficient.

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: three sentences covering action, context, and return format. Every sentence serves a purpose, and the most important information is front-loaded.

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 no parameters and a simple listing function, the description is complete. It explains what the tool does, the scope, and the return type. The presence of an output schema further covers return structure, and the description adds key context about modifiability.

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 no parameters, so the baseline is 4. The description adds meaningful context by specifying the scope ('owned by current session') and return type, which provides value beyond the empty schema.

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 that the tool lists sandbox databases owned by the current session. It distinguishes itself from the sibling 'show_databases' by specifying 'sandbox' and 'owned by current session', making its purpose specific and differentiated.

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 explicitly states that only these databases can be modified, implying the tool should be used when the agent needs to identify modifiable databases. While it doesn't directly contrast with siblings like 'show_databases', the context is clear enough for an AI agent to infer appropriate use cases.

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