terminate_activity

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

The description uses 'Forcefully' to imply destructive or irreversible behavior, but with no annotations provided, it fails to disclose effects, authorization requirements, rate limits, or what happens upon termination. The behavioral picture is incomplete.

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 extremely concise at one sentence, which is efficient, but it omits critical information that a user needs to correctly invoke the tool. Conciseness should not come at the cost of clarity.

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?

The tool has 3 parameters, no output schema, and no annotations. The description does not specify return values, side effects, or error conditions, leaving the agent under-informed about the tool's full behavior.

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 coverage for parameters is 100%, so the schema already documents each field. The description adds no additional meaning beyond the resource name; it does not explain how the parameters relate to the termination process or provide contextual examples.

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 'terminate' and identifies 'standalone activity execution' as the resource, making the core action clear. However, it does not distinguish from sibling tools like 'cancel_activity' or 'batch_terminate_activities', which may have similar purposes.

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 is provided on when to use this tool versus alternatives such as 'cancel_activity' or 'batch_terminate'. There is no mention of prerequisites, exclusions, or typical use cases.

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