glyphdna_mqtt_sub

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavioral traits: 'Subscribe once', 'waits for one message', and 'over TLS'. But it does not mention what happens on timeout, whether the message payload is returned, or connection lifecycle details.

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 compact sentences with no filler. The core behavior is front-loaded, and the argument list is kept minimal and readable.

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 one-shot MQTT subscribe with no output schema, the description covers the essential parameters and core behavior. However, it lacks return-value semantics and timeout/error behavior, which an agent would need to correctly consume the result.

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 is empty aside from additionalProperties true, so the description is the only source of parameter information. It compensates by naming 'creds {username, password}', 'topic', and 'timeout_s', but it omits types, formatting, and defaults.

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 and resource: 'Subscribe once to an MQTT topic over TLS (waits for one message).' It clearly communicates the operation, the transport, and the one-shot blocking behavior, which distinguishes it from sibling tools like glyphdna_mqtt_pub.

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 context is clear: this tool receives a single MQTT message rather than publishing one, which implies when it should be used versus glyphdna_mqtt_pub. However, it does not explicitly name alternatives or state when not to use this tool.

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