delete_topic

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states 'Delete an MQTT topic' without mentioning the destructive nature, the need for confirmation (confirm_write), the availability of dry_run, or any side effects. The schema hints at these safety mechanisms, but the description does not elaborate.

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 short sentence, which is concise in length, but it is under-specified for a tool with three parameters, an output schema, and destructive semantics. It omits essential information, so it is not appropriately sized for the tool's complexity.

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?

The description provides only a minimal purpose statement and lacks any information about usage context, parameter semantics, behavioral details, or safety considerations. Although an output schema exists, the description itself is insufficient for an agent to select and correctly invoke this tool in a realistic workflow.

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 0%, and the description does not explain any of the three parameters (dry_run, payload, confirm_write). An agent has no way to infer what these parameters mean or how to set them from the description alone.

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 (delete) and the resource (MQTT topic), which distinguishes it from sibling tools like list_topics, describe_topics, and configure_topic. It is specific and unambiguous.

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 no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites, conditions, or contrasting scenarios with the many related sibling tools. For example, it doesn't say when to use delete_topic instead of configure_topic.

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