install_integration

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

With no annotations, the description carries the burden. It discloses key behaviors: no in-place update (must delete), and restart requirement. This is critical for a mutation tool. It doesn't cover permissions or side effects, but it's substantial.

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 sentences, front-loaded with the purpose, then caveats. No waste; every clause adds essential information.

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 operation and critical prerequisites but lacks explanation of host and dry_run. With an output schema present, return values are covered, but parameter semantics remain incomplete, making it only partially complete.

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 explain parameters. It implies file_path (the archive), but host and dry_run are entirely unexplained. This is a significant gap for an agent trying to invoke correctly.

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 a specific action (install), a specific resource (custom driver from .tar.gz), and a location (this machine). It clearly distinguishes from siblings like delete_integration or restart_integration by focusing on installation.

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?

It provides crucial context: no in-place update, delete old driver first, and restart required. This implicitly guides when to use (fresh installs) and the necessary steps. It doesn't explicitly name alternative tools but gives clear operational instructions.

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