get_field_values

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

Description mentions 'cached' values, indicating a read operation with potential staleness. However, no elaboration on cache behavior (e.g., what happens when cache is empty) or any other behavioral traits. Without annotations, more detail would be beneficial.

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?

Single sentence, 9 words. No redundancy, front-loaded verb. Every word 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?

No output schema, no annotations. The description omits return format, limitations (e.g., caching behavior), and does not guide the agent on error cases. For a tool with many siblings, more context is needed.

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% parameter description coverage at the top level. The description does not add any meaning beyond the schema's 'Field ID' for the nested id. With low 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?

Description clearly states action (Get) and resource (cached distinct values for a field) from Metabase. Specifically distinguishes itself from other get_* tools by focusing on cached distinct values.

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 vs siblings like get_field or search_field_values. Missing prerequisites or when-not-to-use scenarios.

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