connect_database

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention whether the connection is read-only, if it has side effects (e.g., creating session state), or what happens on failure. The auto-detection behavior is disclosed, but other behavioral traits are missing.

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 concise and front-loaded with the primary action. The Args and Returns sections are standard and informative, though the first sentence and the Args section slightly overlap. There is no wasted text.

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?

While the tool is simple, the description omits critical context such as whether the connection is persistent, whether it must be called once per session, and what constitutes a successful or failed connection. Given the lack of annotations and output schema details, more behavioral context is needed.

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 description fully explains the only parameter, 'database_path', stating it is optional and that auto-detection is used if not provided. This adds meaningful context beyond the input schema, which only lists the parameter name and default.

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 action ('Connect to the rekordbox database') with a specific verb and resource. It distinguishes itself from sibling tools that focus on track management, playlists, or analysis rather than establishing a database connection.

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 this is the setup step for other tools, but it does not explicitly state when to use it versus alternatives or when to specify a path versus rely on auto-detection. Some guidance on prerequisites or when auto-detection might be insufficient would improve clarity.

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