extensions_list

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. The verb 'List' does imply a read-only, non-mutating operation, and the mention of 'enabled and install type' hints at the kind of information returned. However, the description does not explicitly state whether there are any side effects, permission implications, or limits on what 'installed' covers.

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?

A single, efficient sentence that front-loads the primary action and resource before adding the key qualifiers. Every word earns its place, and there is no redundant or filler content.

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?

For a simple no-parameter list tool with no output schema, the description provides the essential scope and indicates what is included in the result. It does not explicitly describe the return shape, but that is a minor omission given how simple and low-risk this operation is.

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?

The tool has zero parameters and the empty schema fully covers that fact, so there is nothing for the description to add. Per the baseline for a zero-parameter tool, this is fully adequate.

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 the specific verb 'List' with the clear resource 'installed Chrome extensions/apps', and adds useful scoping details ('including enabled and install type'). It is immediately distinguishable from sibling tools like extension_get and extension_set_enabled, which target individual extensions rather than listing all of them.

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 or implicit guidance about when to prefer this tool over alternatives such as extension_get, extension_set_enabled, or devtools-related tools. There is no mention of when this list is needed, or when another extension-related sibling would be more appropriate.

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