delete_topic

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

With no annotations, the description carries the full burden of disclosing behavior. It clearly states the destructive action ('Delete') and the HTTP method, which is transparent at a basic level. However, it does not mention whether deletion is permanent, irreversible, or whether it affects related resources like contacts or campaigns.

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 entire description is one short sentence that includes the action, resource, and endpoint. There is no redundant or filler content, and every word contributes to understanding the tool.

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-parameter delete operation with no output schema, the description provides enough call-level context: the action, resource, and endpoint. It could additionally mention what happens after deletion (e.g., success response shape), but this is a minor gap for such a simple operation.

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 already documents the single 'id' parameter at 100% coverage with 'The topic id.' The description adds no additional semantic meaning, but the schema is sufficient, so the baseline score of 3 is appropriate.

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 ('Delete') and resource ('topic'), and reinforces it with the HTTP endpoint 'DELETE /topics/:id'. This makes the tool's action unambiguous and distinguishes it from siblings like create_topic, update_topic, get_topic, and list_topics.

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 about when to use this tool versus alternatives, nor any constraints such as prerequisites or consequences. The agent is left to infer that this is for removing a topic rather than updating or listing it.

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