arango_set_focused_database

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

No annotations are provided, so the description carries the full burden. It explains the session-wide effect and how to revert. It does not mention authorization or scope details, but for a simple setter, this is sufficient. Slight gap on whether the focus persists across different connections.

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 two sentences, efficient and front-loaded. Every sentence provides essential information: first states the action, second explains the effect and how to unset. No unnecessary details.

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 simplicity of the tool (single optional parameter, no output schema, no annotations), the description is largely complete. It covers setting, unsetting, and the session scope. One could argue it could mention whether the focus applies only to the current connection, but it's a minor gap.

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 coverage is 100% (one parameter fully described). The description adds meaningful context by explaining that setting the database affects all subsequent tool calls unless overridden, which goes beyond the schema description. This helps the agent understand the parameter's impact.

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 tool's purpose: setting the focused database for the current session. It specifies the verb 'set', the resource 'focused database', and the scope 'current session', distinguishing it from sibling tools like 'arango_get_focused_database'.

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 explains when to use the tool (to set a focused database) and when to unset it (pass None or empty string). It also mentions that subsequent calls will use this database unless overridden, providing context. However, it does not explicitly mention alternatives like using the 'database' parameter directly on each tool call.

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