batch_terminate_activities

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

No annotations are provided, so the description must disclose behavioral traits. It mentions termination via query and limit details but omits side effects, irreversibility, success/failure reporting, or how concurrency and reason parameters affect execution.

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 concise sentence front-loaded with the primary action. However, it omits important details about other parameters and behavior, slightly reducing efficiency.

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?

Given no output schema and no annotations, the description is insufficient. It lacks explanation of return values, error handling, behavior when limit is exceeded, and the role of concurrency and reason, making the tool's complete behavior unclear.

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 100%, but the description adds minimal value beyond what the schema already provides (e.g., limit default 100 is in both). It does not elaborate on query format, reason usage, or concurrency behavior.

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 'Terminate multiple standalone activities matching a query', specifying a verb, resource, and method. It distinguishes from siblings like singular terminate_activity and batch_cancel_activities.

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 only mentions controlling batch size via 'limit', but provides no guidance on when to use this tool versus alternatives like cancel_activity or batch_cancel_activities, and no when-not-to-use context.

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