Connect MQTT IoT bus

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, providing the safety profile. The description adds the 'policy-gated operator commands' nuance and 'scaffold' language, but does not disclose side effects such as broker connectivity requirements, component creation details, or error handling.

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, front-loaded sentence with no wasted words. It concisely communicates the primary action and purpose.

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?

Given the tool's complexity (9 params, no output schema), the description is too terse. It does not explain what a 'DAT bus scaffold' entails, what happens on execution, or what the effects are. The low schema coverage further increases the need for a more detailed description.

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 description does not explain any of the 9 parameters. Schema description coverage is only 44%, leaving qos, active, client_id, broker_port, and topic_count without descriptions. The high-level purpose does not compensate for the missing parameter explanations.

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 'Create an MQTT Client DAT bus scaffold' with specific use cases (IoT sensors, installation telemetry, policy-gated operator commands). This distinguishes it from sibling tools like connect_kafka_event_bus or connect_redis_pubsub_bus.

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 clear context for when to use the tool (IoT sensor data, telemetry, operator commands) but does not explicitly mention when not to use it or name alternative tools. It implies usage rather than stating exclusions.

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