Connect InfluxDB time-series bridge

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds context about token-safety warnings and adapter notes, which gives some behavioral insight. However, it omits side effects, permission requirements, or reversibility. No contradiction with annotations.

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 a single, focused sentence that leads with the action verb and lists the key deliverables without redundant or extraneous wording.

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?

With 10 parameters, no output schema, and a nontrivial operation, the description is under-specified. It does not describe expected results, return values, prerequisites, or how the parameters collectively shape the scaffold. It also lacks integration guidance among the many similar tools.

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% (2 of 10 parameters documented). The description mentions constructs like measurement maps and field maps that roughly relate to measurement_count, field_count, and adapter_mode, but it does not explain any parameter directly or compensate for the missing schema descriptions.

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 ('Create') and the resource ('InfluxDB telemetry scaffold') with specific components (measurement maps, field maps, query/write adapter notes, token-safety warnings). This distinguishes it from other connectors by explicitly targeting InfluxDB and its scaffold contents.

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 offers no guidance on when to use this tool versus the many sibling connector/bridge tools. It does not state prerequisites, use cases, or recommend alternatives, leaving the agent to infer based solely on the name.

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