database_overview

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

With no annotations, the description carries more burden. It helpfully discloses the key returned fields and implies a read-only overview, but it does not explicitly state that it is non-mutating, whether it requires an open connection, or how the overview is structured.

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?

A single, front-loaded sentence that identifies the tool's purpose and enumerates the useful outputs without any filler. Every phrase contributes to understanding what the overview returns.

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 zero-parameter overview tool with no output schema, the description is nearly complete: it names the main fields returned. It could be strengthened with a brief note on when to choose it over list_tables or describe_table, but the core context is present.

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 takes zero parameters, so the baseline is 4. The description correctly does not invent parameter details and simply describes the no-argument overview behavior.

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 resource and summarizes exactly what the overview contains: path or server URL, connection mode, tables, and ANN readiness. It is clearly distinct from more granular siblings such as list_tables or describe_table, though it does not explicitly name those alternatives.

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 phrase 'high-level overview' implies this is a summary/orientation tool, but there is no explicit guidance on when to use it instead of list_tables, describe_table, or other siblings. Usage is inferable but not specified.

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