Connect AIS vessel bus

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

Annotations already indicate that this is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds context about 'sanitized vessel rows' and 'receiver/privacy notes', which hints at data sanitization and privacy handling, but it does not elaborate on side effects, permissions, or reversibility.

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 sentence that is front-loaded with the primary action and resource, and it enumerates scaffold components compactly. It is concise without unnecessary filler, though the list format could be clearer.

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 limited annotation detail, a high-level one-sentence overview is insufficient. The description does not explain what the scaffold includes beyond a few components, nor does it describe return values or how the scaffold is structured, leaving gaps for a tool of this complexity.

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 have descriptions). The description mentions concepts like 'zone maps' and 'route hints' that loosely map to zone_count and route_count, but it does not explain individual parameters such as adapter_mode, adapter_url, vessel_count, or waterway_label. The description does not compensate for the low schema coverage.

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 uses a specific verb 'Create' and identifies the resource as an 'AIS vessel scaffold', listing key components (sanitized vessel rows, zone maps, route hints, adapter source, receiver/privacy notes). It clearly distinguishes the tool's purpose from generic 'connect' tools, though the name says 'connect' while description says 'create', causing slight ambiguity.

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?

There is no guidance on when to use this tool versus alternatives like connect_adsb_aircraft_bus or other connect_* bus tools. No exclusions or prerequisites are mentioned, so the agent must infer usage from the name alone.

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