mqtt_publish

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

With no annotations, the description carries the full behavioral burden and largely fails it: it says nothing about delivery guarantees, connection/broker prerequisites, error behavior on failure, or whether the call blocks. The only behavioral hints (QoS, retain) live in the schema, not the description.

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?

Two short sentences, the action front-loaded and the rationale second. No redundancy, no filler, immediately scannable.

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 4-parameter publish tool with no annotations and no output schema, the description is minimally sufficient on the 'what' but silent on operational context an agent would want (required connection state, failure modes, whether a response is returned).

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 100%, so topic, message, qos, and retain are already fully documented with types, defaults, and an example. The description adds no semantic detail beyond the schema, which is the baseline expectation.

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?

States a specific verb and resource ('Publish a message to an MQTT topic'), which is unmistakably distinct from the subscribe/read/list siblings. It does not, however, explicitly name or contrast itself with any sibling tool.

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 second sentence gives a use context ('sending test data or triggering actions on the broker'), which implies when the tool is appropriate. There is no explicit when-not guidance or reference to alternatives such as mqtt_subscribe for consuming messages.

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