select-database

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

The description lacks disclosure of behavioral traits beyond the basic action. With no annotations, it should explain what 'switch to' entails (e.g., is it stateful? Errors on invalid db?). It only states the action without side effects or requirements.

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?

Single sentence with no wasted words, but could be restructured to include context like usage conditions. Slightly too brief for a tool that affects state.

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 (one param, no output), the description is minimal. It doesn't explain the effect on subsequent operations (e.g., query-documents) or error handling, leaving some gaps in completeness for a state-changing tool.

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 covers the sole parameter (100% coverage), and the tool description adds no additional meaning beyond 'database to select'. Baseline score of 3 applies as schema already explains the parameter 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 uses a specific verb ('Switch to') and resource ('database context'), clearly stating the action and what it affects. It distinguishes itself from sibling tools like 'query-documents' or 'initialize-connection' by focusing on context switching.

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?

No explicit guidance on when to use this tool versus alternatives, such as needing an initialized connection first or when to select a different database. Siblings like 'initialize-connection' suggest a prerequisite, but this is not mentioned.

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