superset_database_connection_info

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 discloses that the URI excludes the password, which is a meaningful behavioral trait for privacy. However, it does not explicitly state that this is a read-only operation or mention any auth/rate-limit considerations, leaving some gaps.

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 very concise and well-structured, with a single sentence front-loading the main purpose followed by a clear Args block. Every word earns its place, making it easy to scan and understand.

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 simple nature of the tool (one parameter, output schema exists), the description covers the core purpose and the critical security note about password omission. It does not explain what 'parameters' means or any operational details, but for this simple read-like tool, it is reasonably complete.

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 schema has 0% description coverage, so the description's 'Args: database_id: Database connection ID' provides basic semantics. It clarifies that the parameter is an ID, but it largely restates the parameter name without adding deeper context, offering only marginal compensation for the schema gap.

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 'Get connection information (URI without password, parameters)' with a specific verb and resource. It is not a tautology and adds a key detail about password exclusion. However, it does not explicitly distinguish from siblings like superset_database_get, which might also return connection details.

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 usage by stating what the tool does, but provides no explicit guidance on when to use it vs alternatives or any exclusions. It lacks context about prerequisites or when to prefer other database-related tools, so only implicit usage is conveyed.

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