Connect InfluxDB time-series bridge

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

The annotations already indicate a mutating, world-open operation. The description adds that it creates a scaffold with maps and adapter notes, and highlights token-safety warnings, which is useful safety context. However, it doesn't disclose whether it overwrites existing scaffolds, modifies parent components, or makes network calls to the endpoint, so there is room for more behavioral detail.

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?

A single, front-loaded sentence with no unnecessary words. It conveys the main action and lists key artifacts without redundancy, making it easy to scan.

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?

The tool has 10 parameters, no output schema, and no description of return values or expected behavior. The one-sentence description offers a high-level summary but is insufficient for an agent to correctly invoke and configure all parameters. It lacks details about defaults, ranges, and how the scaffold integrates with the rest of the project.

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 description coverage is only 20% (name and parent_path). The description does not mention any of the other eight parameters (org, bucket, field_count, adapter_mode, endpoint_url, poll_seconds, measurement_count) or their meaning. Terms like 'measurement maps' and 'field maps' loosely relate to measurement_count and field_count but there is no explicit mapping, leaving the agent to guess.

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 it creates an InfluxDB telemetry scaffold and lists specific outputs (measurement maps, field maps, adapter notes, token-safety warnings). This distinguishes it from sibling connect_* tools that target other systems. However, the phrase 'telemetry scaffold' is somewhat jargon-heavy and doesn't explicitly clarify what integration step it performs.

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 explicit when-to-use guidance, prerequisites, or alternatives are provided. The description implies it's for setting up InfluxDB telemetry but doesn't mention the need for a parent path or how this differs from similar create_* and connect_* tools. Users are left to infer when to choose this tool.

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