delete_integration

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

With no annotations, the description carries the full burden of behavioral disclosure. It thoroughly explains the destructive scope: removing the driver, its instance, all entities, and stripping button mappings and page items. It also warns to read a preview, implying a dry-run or confirmation step. However, it does not explicitly mention permissions, reversibility, or the role of the dry_run parameter, which could be critical for safe use.

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 with no filler. The primary action and full scope are front-loaded, and the safety instruction is concise. Every word adds value, and the structure is clear and scannable.

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 description covers the main destructive behavior well and mentions a preview, but it omits key context such as the purpose of dry_run and host, and it does not describe the output format (though an output schema exists). Given the tool's complexity (cascading deletions) and the lack of annotations, the description is adequate but not comprehensive, leaving the agent to infer parameter roles and prerequisites.

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. It only implies that driver_id identifies the driver to remove, but does not explain the host or dry_run parameters. The mention of 'preview' hints at dry_run but does not clarify its default or behavior. Since two of three parameters are undocumented, the description adds minimal semantic value beyond the schema.

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 a specific action: removing a driver and all its associated entities, button mappings, and page items. It names the resource (driver) and the full scope, distinguishing it from similar tools like delete_integration_instance, which likely deletes only an instance. The verb 'Remove' is specific and the object is well-defined.

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 explicit guidance on when to use this tool versus alternatives. It does not mention that delete_integration_instance exists for instance-only removal, nor does it provide conditions or exclusions. The only hint is 'Read the preview before applying,' which is a caution about the destructive nature, not about when to select this tool.

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