delete_activity_logs

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states that logs are deleted, but does not clarify irreversibility, permission requirements, the exact time range semantics ('from' could mean after or before), user/workspace scoping, or what happens to logs not matching the filter. The description is notably vague for a destructive operation.

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 sentences, front-loads the primary action, and avoids redundant phrasing. It is appropriately concise without being under-specified, given the simplicity of 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?

Despite having no output schema and no annotations, the description does not explain critical context such as the exact semantics of 'from a specific datetime' (e.g., inclusive, before/after), potential side effects, or how this relates to list_activity_logs. For a destructive tool with minimal structured metadata, this description falls short of being complete.

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 describes both parameters fully (datetime as ISO 8601, delete_unassigned_logs as filtering null user_id). The description adds minimal value beyond restating the schema's flag behavior. Since schema coverage is 100%, a score of 3 is appropriate per the baseline.

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 activity logs') and specifies a key scope ('from a specific datetime'), distinguishing it from siblings like list_activity_logs and other delete_* tools. The optional flag behavior is also mentioned, making the purpose 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 explicit guidance on when to use this tool versus alternatives such as list_activity_logs, nor does it mention prerequisites, exclusions, or scenarios where deletion would be inappropriate. It only hints at a specific use case for the optional flag, which is insufficient guidance.

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