get_database

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

The annotation readOnlyHint=true already establishes safety, and the description's 'Retrieve' aligns. The description adds that the tool returns connection details and schema, which is more about output content than behavioral traits. No additional side effects, permissions, or rate limits are disclosed, so the value beyond annotations is limited.

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 sentence with no redundancy. The verb, resource, and use case are packed efficiently; every phrase earns its place.

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 one-parameter getter with full schema documentation and an output schema, the description is complete. It clearly states what the tool retrieves and when to use it, making selection and invocation straightforward.

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?

With 100% schema coverage, the only parameter database_id is already fully described as 'The ID of the database to retrieve' in the schema. The tool description adds only the modifier 'specific,' which does not significantly enhance parameter understanding, so the baseline of 3 is appropriate.

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 'Retrieve' to clearly indicate a read operation, specifies 'specific Metabase database' to distinguish it from list_databases, and lists expected content ('connection details and schema'), making the purpose unambiguous and distinct from sibling tools.

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 explicitly states 'use this to examine database properties or troubleshoot connections,' providing concrete when-to-use guidance. However, it does not mention alternative tools or exclusionary scenarios, so it lacks full when-not-to-use guidance.

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