get_database_id_fields

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

No annotations provided, so the description carries the full burden. It only states it 'gets' data, implying a safe read, but does not disclose any behavioral traits (e.g., auth requirements, rate limits, or what happens if the database does not exist). Minimal information.

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 a single, concise sentence with no unnecessary words or redundancies. It front-loads the core purpose.

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 no output schema and no annotations, the description is minimal. It covers the basic purpose but lacks details on return format, prerequisites, or edge cases. For a simple get tool with one required parameter, it is adequate but not thorough.

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 does not add any parameter details beyond the input schema, which already provides descriptions for 'id' and 'include_editable_data_model'. Since schema coverage is effectively 100% (both parameters have descriptions in the schema), baseline 3 applies; the description adds no extra value.

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?

Description clearly states the tool retrieves all ID-type fields for a database in Metabase. It uses a specific verb ('get') and resource ('ID-type fields for a database'), and distinguishes from sibling tools like 'get_database_fields' which likely return all 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_fields' or 'get_field'. No context on prerequisites or exclusions. The description is a single sentence with no usage hints.

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