get_database_metadata

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

No annotations are provided, so the description must fully disclose behavior. It only states the action (get metadata) but does not mention side effects, permissions, or any constraints beyond the input ID. The description is minimal and leaves the agent uninformed about read-only nature or potential impacts.

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 at one sentence with no unnecessary words. However, it could be slightly more structured to include key details like what the output contains.

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?

The description lacks information about the output format or structure, which is important for a metadata retrieval tool. No output schema is provided, and the description does not clarify whether it returns tables, fields, or other nested information. Given the nested input schema, the agent may need more context.

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?

Only one parameter 'id' exists with schema description 'Database ID', which is already in the input schema. The tool description does not add any additional meaning or context beyond what the schema provides. With 0% schema description coverage, the description should compensate but fails to do so.

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 retrieves database metadata including tables and fields from Metabase. It uses a specific verb 'Get' and identifies the resource 'database metadata', distinguishing it from siblings like 'get_database' (basic info) and 'get_database_fields' (only fields).

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 guidance on when to use this tool versus alternatives like 'get_database' or 'get_table_metadata'. Lacks information about prerequisites or when it's appropriate to call.

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