get_field_summary

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

No annotations are provided. The description does not disclose behavioral traits such as what kind of statistics are returned, permission requirements, performance implications, or response structure. The minimal description leaves the agent uninformed about the tool's behavior.

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 (one sentence) but sacrifices completeness. It is front-loaded but does not contain all necessary information.

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 complexity of the domain (many sibling field-related tools) and the lack of output schema, the description fails to explain what 'summary statistics' entails (e.g., count, min, max, distribution). The agent cannot determine if this tool meets its needs without additional 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?

The schema has low description coverage (0% per context signals). The description adds no additional meaning to the parameter 'id' beyond the schema's basic 'The field ID'. It does not specify format, constraints, or how the ID relates to summary statistics.

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 action ('Get'), the resource ('summary statistics for a field'), and the context ('in Metabase'). It distinguishes itself from sibling tools like 'get_field', 'get_field_values', and 'get_field_related' by specifying 'summary statistics'.

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 provides no guidance on when to use this tool versus alternatives such as 'get_field' or 'get_field_values'. There is no mention of prerequisites, scenarios, or exclusions.

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