automation_task_templates_delete_many

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

No annotations are provided. The description says 'Disable' but the HTTP method is DELETE, which is contradictory and unclear. No information about side effects, permissions, or whether the operation is reversible. The description fails to disclose essential behavioral traits.

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 short but unclear and poorly structured. It repeats the tool name and HTTP method, which are already in the title. The sentence tries to convey too much in a single line without proper separation of concerns.

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?

No output schema is present. The description does not explain what the tool returns, how deletions are handled (soft vs hard), or any limits (e.g., batch size). For a 'delete many' operation, this is critically incomplete.

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 schema has 100% coverage for two parameters (q and body). The description adds minimal value by stating 'Required: q' and 'Requires a JSON request body', but this contradicts the schema where both parameters are optional (default null). This creates confusion rather than clarity.

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 states 'Disable instance of the objects' which is ambiguous—does it disable or delete? The HTTP method DELETE suggests deletion, but the word 'disable' is confusing. There is no differentiation from sibling delete tools like 'endpoint_delete_many' or 'user_invitation_delete'.

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?

No guidance on when to use this tool versus alternatives. No prerequisites, context, or exclusions provided. The description only states 'Required: q' but the schema shows q is optional, adding confusion.

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