install_extension

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

No annotations provided, and the description does not disclose behavioral details such as whether installation is synchronous, what happens if the extension is already installed, permission requirements, or side effects. The schema's 'permanent' parameter hints at signing requirements, but the description adds no behavioral context beyond listing methods.

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, no wasted words. The first sentence states the purpose, the second lists supported types. Ideal length for quick comprehension.

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?

Covers the main installation methods but lacks important context: no description of return value, error scenarios, or implications of the 'permanent' flag. For a mutation tool with no output schema, more detail on behavior and prerequisites would be beneficial.

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 is 100%, so the schema already documents all parameters. The description adds a brief grouping of installation methods matching the 'type' enum, but does not provide additional meaning for individual parameters beyond what the schema gives. Baseline score of 3 is appropriate.

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 the tool installs a Zen extension using WebDriver BiDi, and lists the three supported data types (archive, base64, unpacked directory). This distinguishes it from the sibling uninstall_extension tool.

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 on when to use which installation method, prerequisites (e.g., need signed extension for permanent install is only in schema), or when to avoid this tool. The description does not help an agent choose between this and other tools.

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