list_field_keys

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

No annotations are provided, so the description carries the burden. 'List' indicates a read-only operation but does not explicitly state safety, permissions, or return behavior. The output schema exists, so return format is covered elsewhere, but other behavioral traits like potential errors are omitted.

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 two sentences plus a compact Args list. It is front-loaded with the core purpose and adds parameter details without unnecessary verbosity.

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 list tool with an output schema and only two parameters, the description covers all essential aspects. No additional context is needed to understand or invoke the tool correctly.

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 input schema has no descriptions (0% coverage), but the description provides clear semantics for both parameters: 'database' is an InfluxDB database name, and 'measurement' is an optional filter. This fully compensates for the schema's lack of detail.

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 lists field keys and their types in a database, with optional filtering by measurement. This distinguishes it from siblings like list_tag_keys and list_measurements, which serve different purposes.

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 implies when to use the tool (to inspect field keys) and mentions the optional measurement filter. It does not explicitly state when to use alternatives or provide exclusions, but the context among sibling list tools is clear enough.

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