influx-show-tag-values

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

With no annotations, the description carries the full burden for behavioral transparency. It only states that it lists values, but does not disclose any potential side effects, performance impacts, authentication needs, or limits. This is minimal.

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?

Two sentences with no wasted words. The first sentence states the core purpose, the second provides usage examples. Very concise and well-structured.

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 simple query tool listing tag values, the description is fairly complete. It could mention that it uses SHOW TAG VALUES or requires a running datasource, but these are implicit. No output schema, but return values are self-explanatory.

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?

Schema coverage is 100% with descriptions for all 4 parameters. The description adds context that the tagKey is for fields like 'host' or 'region', which is helpful but not substantial. Baseline is 3.

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 using the verb 'List' and specifies the resource 'tag values for a specific tag key in an InfluxDB measurement'. It distinguishes from sibling tools like influx-show-tag-keys (lists keys) and influx-show-field-keys (lists fields) by focusing on 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?

The description provides context by mentioning use cases like discovering hostnames, environments, regions. However, it does not explicitly state when not to use the tool or suggest alternatives, which is a gap.

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