accelo_delete_activity

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

No annotations are provided, so the description carries the full behavioral burden, yet it says only that an activity is deleted. It does not disclose whether the delete is permanent or reversible, whether special permissions are required, or what happens to dependent records. The word "delete" at least signals a destructive mutation, which keeps it above a 1.

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 core statement is front-loaded and free of filler, but the "Args:" block is a raw docstring artifact that adds structural noise rather than value for a single self-evident parameter.

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 destructive, irreversible operation with no annotations and no output schema, the description is too thin: it omits reversibility, permission requirements, and any notion of what a successful call returns. An agent cannot safely reason about the consequences of invoking it.

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?

With one parameter at 0% schema coverage, the description does supply the only documentation available: id is the "Activity ID to delete." That confirms the identifier's meaning but adds no format, type, or sourcing detail beyond the obvious.

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 ("Delete an activity"), so an agent knows exactly what operation it performs. However, it offers no differentiation from siblings like accelo_update_activity, accelo_get_activity, or accelo_cancel_timer, so the agent must infer scope from the name alone.

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 on when to use this versus alternatives such as updating or cancelling an activity, and no mention of prerequisites or consequences. The agent gets no context for choosing this tool over the update/get variants.

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