remove_scope_entities

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

With no annotations, the description carries the burden of disclosing side effects, and it does warn that button mappings and page items referencing the entities are also removed and that a preview should be read first. However, it does not state whether the action is reversible, what permissions are needed, or what 'stop an activity or macro' concretely entails.

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?

Two efficient sentences: the first states the core action, the second surfaces the most important side effect and a practical caution. There is no filler or redundant repetition of schema field names.

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 five parameters, no annotations, and a relatively complex destructive behavior, yet the description addresses none of the parameters and leaves the preview/dry-run workflow unexplained. The output schema exists, so return values are covered, but an agent still lacks enough context to invoke this tool safely and correctly.

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 0%, so the description must compensate, but it only vaguely implies that entity_ids are the entities being removed. It does not explain scope_id, host, scope, or dry_run, even though dry_run is critical to the preview-and-apply workflow hinted at in the text.

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 identifies the operation as stopping an activity or macro by removing its entities, and it states the cascading removal of dependent button mappings and page items. It distinguishes itself from sibling tools like add_scope_entities or list_scope_entities through the explicit 'remove' semantics and destructive side effects, though it does not name those siblings.

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 gives no guidance on when to choose this tool over alternatives, such as add_scope_entities or delete_integration. It offers a caution about reading the preview but does not explain prerequisites, exclusions, or how to select between this and related scope-entity tools.

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